From: William Lee Irwin III <wli@holomorphy.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch] hugepage allocator cleanup
Date: Wed, 25 Jan 2006 19:04:24 -0800 [thread overview]
Message-ID: <20060126030424.GH7655@holomorphy.com> (raw)
In-Reply-To: <20060125165208.GC25666@wotan.suse.de>
On Wed, Jan 25, 2006 at 08:32:43AM -0800, William Lee Irwin III wrote:
>> Just yanking the page refcount affairs out of update_and_free_page()
>> should suffice. Could I get things trimmed down to that?
>>
On Wed, Jan 25, 2006 at 05:52:08PM +0100, Nick Piggin wrote:
> I could remove the first set_page_count, and make the second conditional
> on the page having a zero refcount... for a 3-liner. But that's kind of
> ugly (if less intrusive), and it is adds seemingly nonsense code if one
> doesn't have the context of my out-of-tree patches.
> Hmm... it's obviously not 2.6.16 material so there is no rush to think
> it over. It is even simple enough that I don't mind carrying with my
> patchset indefinitely.
After I thought about it, alloc_fresh_huge_page() does enqueue pages
with refcounts of 1, where free_huge_page() (called from the freeing
hook in page[1].mapping) enqueues pages with refcounts of 0, so it
would actually make sense (and possibly prevent leaks) to take the
whole patch as-is.
-- wli
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-01-26 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 9:11 Nick Piggin
2006-01-25 15:05 ` William Lee Irwin III
2006-01-25 15:18 ` Nick Piggin
2006-01-25 16:32 ` William Lee Irwin III
2006-01-25 16:52 ` Nick Piggin
2006-01-26 3:04 ` William Lee Irwin III [this message]
2006-01-26 14:19 ` Nick Piggin
2006-01-26 3:09 ` William Lee Irwin III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060126030424.GH7655@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox