From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Phillips Subject: Re: [RFC][patch 0/2] mm: remove PageReserved Date: Wed, 10 Aug 2005 07:27:46 +1000 References: <42F57FCA.9040805@yahoo.com.au> <1123598952.30257.213.camel@gaston> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508100727.47698.phillips@arcor.de> Sender: owner-linux-mm@kvack.org Return-Path: To: Hugh Dickins Cc: Benjamin Herrenschmidt , Nick Piggin , linux-kernel , Linux Memory Management , Linus Torvalds , Andrew Morton , Andrea Arcangeli List-ID: On Wednesday 10 August 2005 01:36, Hugh Dickins wrote: > On Tue, 9 Aug 2005, Benjamin Herrenschmidt wrote: > > - We already have a refcount > > - We have a field where putting a flag isn't that much of a problem > > - It can be difficult to get page refcounting right when dealing with > > such things, really. > > Probably easier to get the page refcounting right with these than with > most. Getting refcounting wrong is always bad. He seems to be arguing for a new debug option. > > In that case, we basically have an _easy_ way to trigger a useful BUG() > > in the page free path when it's a page that should never be returned to > > the pool. > > As bad_page already does on various other flags (though it clears those, > whereas this one you'd prefer not to clear). Hmm, okay, though I'm not > sure it's worth its own page flag if they're in short supply. Nineteen out of 32 officially spoken for so far, with some out of tree patches regarding the remainder with desirous eyes no doubt. I think that qualifies as short supply. But it is not just that, it is the extra cost of understanding and auditing the features implied by the flags, particularly bogus features. Regards, Daniel -- 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/ . Don't email: email@kvack.org