From: Dave Hansen <haveblue@us.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 0/2 Buddy allocator with placement policy (Version 9) + prezeroing (Version 4)
Date: Thu, 10 Mar 2005 09:37:47 -0800 [thread overview]
Message-ID: <1110476267.16432.27.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0503101421260.2105@skynet>
On Thu, 2005-03-10 at 14:31 +0000, Mel Gorman wrote:
> > > There are 2 kinds of sections: user and kernel. The traditional
> > > ZONE_HIGHMEM is full of user sections (except for vmalloc).
>
> And PTEs if configured to be allocated from high memory. I have not double
> checked but I don't think they can be trivially reclaimed.
We've run into a couple of these pieces of highmem that can't be
reclaimed. The latest one are pages for the new pipe buffers. We could
code these up with a flag something like __GFP_HIGHMEM_NORCLM, that is
__GFP_HIGHMEM in the normal case, but 0 in the hotplug case (at least
for now).
> > > Any
> > > section which has slab pages or any kernel caller to alloc_pages() is
> > > a kernel section.
>
> Slab pages could be moved to the user section as long as the cache owner
> was able to reclaim the slabs on demand.
At least for the large consumers of slab (dentry/inode caches), they
can't quite reclaim on demand. I was picking Dipankar's brain about
this one day, and there are going to be particularly troublesome
dentries, like "/", that are going to need some serious rethinking to be
able to forcefully free.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2005-03-10 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 19:39 Mel Gorman
2005-03-07 23:59 ` Dave Hansen
2005-03-10 14:31 ` Mel Gorman
2005-03-10 17:22 ` Paul Jackson
2005-03-10 18:16 ` Dave Hansen
2005-03-10 20:11 ` Paul Jackson
2005-03-10 20:17 ` Dave Hansen
2005-03-10 20:54 ` Paul Jackson
2005-03-14 14:10 ` Mel Gorman
2005-03-14 19:10 ` Paul Jackson
2005-03-10 17:37 ` Dave Hansen [this message]
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=1110476267.16432.27.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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