[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111027215243.GA31644@infradead.org>
Date: Thu, 27 Oct 2011 17:52:43 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
Cc: Christoph Hellwig <hch@...radead.org>,
David Rientjes <rientjes@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Konrad Wilk <konrad.wilk@...cle.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Seth Jennings <sjenning@...ux.vnet.ibm.com>, ngupta@...are.org,
levinsasha928@...il.com, Chris Mason <chris.mason@...cle.com>,
JBeulich@...ell.com, Dave Hansen <dave@...ux.vnet.ibm.com>,
Jonathan Corbet <corbet@....net>, Neo Jia <cyclonusj@...il.com>
Subject: Re: [GIT PULL] mm: frontswap (for 3.2 window)
On Thu, Oct 27, 2011 at 02:49:31PM -0700, Dan Magenheimer wrote:
> If Linux truly subscribes to the "code rules" mantra, no core
> VM developer has proposed anything -- even a design, let alone
> working code -- that comes close to providing the functionality
> and flexibility that frontswap (and cleancache) provides, and
> frontswap provides it with a very VERY small impact on existing
> kernel code AND has been posted and working for 2+ years.
> (And during that 2+ years, excellent feedback has improved the
> "kernel-ness" of the code, but NONE of the core frontswap
> design/hooks have changed... because frontswap _just works_!)
It might work for whatever defintion of work, but you certainly couldn't
convince anyone that matters that it's actually sexy and we'd actually
need it. Only actually working on Xen of course doesn't help.
In the end it's a bunch of really ugly hooks over core code, without
a clear defintion of how they work or a killer use case.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists