From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id 4F4A06B002D for ; Thu, 27 Oct 2011 17:49:41 -0400 (EDT) MIME-Version: 1.0 Message-ID: <75efb251-7a5e-4aca-91e2-f85627090363@default> Date: Thu, 27 Oct 2011 14:49:31 -0700 (PDT) From: Dan Magenheimer Subject: RE: [GIT PULL] mm: frontswap (for 3.2 window) References: In-Reply-To: <20111027211157.GA1199@infradead.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Hellwig , David Rientjes Cc: Linus Torvalds , linux-mm@kvack.org, LKML , Andrew Morton , Konrad Wilk , Jeremy Fitzhardinge , Seth Jennings , ngupta@vflare.org, levinsasha928@gmail.com, Chris Mason , JBeulich@novell.com, Dave Hansen , Jonathan Corbet , Neo Jia > From: Christoph Hellwig [mailto:hch@infradead.org] > Sent: Thursday, October 27, 2011 3:12 PM > To: David Rientjes > Cc: Dan Magenheimer; Linus Torvalds; linux-mm@kvack.org; LKML; Andrew Mor= ton; Konrad Wilk; Jeremy > Fitzhardinge; Seth Jennings; ngupta@vflare.org; levinsasha928@gmail.com; = Chris Mason; > JBeulich@novell.com; Dave Hansen; Jonathan Corbet; Neo Jia > Subject: Re: [GIT PULL] mm: frontswap (for 3.2 window) >=20 > On Thu, Oct 27, 2011 at 01:18:40PM -0700, David Rientjes wrote: > > Isn't this something that should go through the -mm tree? >=20 > It should have. It should also have ACKs from the core VM developers, > and at least the few I talked to about it really didn't seem to like it. Yes, it would have been nice to have it go through the -mm tree. But, *sigh*, I guess it will be up to Linus again to decide if "didn't seem to like it" is sufficient to block functionality that has found use by a number of in-kernel users and by real shipping products... and continues to grow in usefulness. 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_!) Perhaps other frontswap users would be so kind as to reply on this thread with their opinions... Dan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org