> From: Pekka Enberg [mailto:penberg@xxxxxxxxxx] > Subject: Re: [RFC/PATCH] zcache/ramster rewrite and promotion > > On Mon, Aug 6, 2012 at 5:07 PM, Dan Magenheimer > <dan.magenheimer@xxxxxxxxxx> wrote: > > I'm OK with placing it wherever kernel developers want to put > > it, as long as the reason is not NIMBY-ness. [1] My preference > > is to keep all the parts together, at least for the review phase, > > but if there is a consensus that it belongs someplace else, > > I will be happy to move it. > > I'd go for core code in mm/zcache.c and mm/ramster.c, and move the > clustering code under net/ramster or drivers/ramster. Hi Pekka -- Thanks for the quick feedback! Hmmm.. there's also zbud.c and tmem.c which are critical components of both zcache and ramster. And there are header files as well which will need to either be in mm/ or somewhere in include/linux/ Is there a reason or rule that mm/ can't have subdirectories? Since zcache has at least three .c files plus ramster.c, and since mm/frontswap.c and mm/cleancache.c are the foundation on which all of these are built, I was thinking grouping all six (plus headers) in the same mm/tmem/ subdirectory was a good way to keep mm/ from continuing to get more cluttered... not counting new zcache and ramster files, there are now 74 .c files in mm/! (Personally, I think a directory has too many files in it if "ls" doesn't fit in a 25x80 window.) Thoughts? Dan _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
