On Tue, May 14, 2013 at 09:37:08AM -0700, Dan Magenheimer wrote: > > Can I get your ack on this pending the other changes? > > I'd like to hear Mel's feedback about this, but perhaps > a compromise to allow for zswap merging would be to add > something like the following to zswap's Kconfig comment: > I think there is a lot of ugly in there and potential for weird performance bugs. I ran out of beans complaining about different parts during the review but fixing it out of tree or in staging like it's been happening to date has clearly not worked out at all. As starting points go, it could be a hell of a lot worse. I do agree that it needs a big fat warning until some of the ugly is beaten out of it. Requiring that it address all the issues such as automatic pool sizing, NUMA issues, proper allocation prior to merging will just end up with an unreviewable set of patches again so lets just bite the bullet because at least there is a chance reviewers can follow the incremental developments. Merging it to drivers will not address anything IMO. -- Mel Gorman SUSE Labs _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
