From: Rohit Seth <rohit.seth@intel.com>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: akpm@osdl.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] earlier allocation of order 0 pages from pcp in __alloc_pages
Date: Thu, 29 Sep 2005 18:32:13 -0700 [thread overview]
Message-ID: <1128043933.3735.26.camel@akash.sc.intel.com> (raw)
In-Reply-To: <719460000.1128034108@[10.10.2.4]>
On Thu, 2005-09-29 at 15:48 -0700, Martin J. Bligh wrote:
> > Try to service a order 0 page request from pcp list. This will allow us to not check and possibly start the reclaim activity when there are free pages present on the pcp. This early allocation does not try to replenish an empty pcp.
> >
> > Signed-off-by: Rohit Seth <rohit.seth@intel.com>
>
> It seems a bit odd to copy more code to do this, which I think we already
> have in buffered_rmqueue? Can we clean up the flow a bit here ... it
> is already looking messy in __alloc_pages with various gotos and crud
> there. I'm not saying what you're trying to do is bad, but the flow
> in there is getting more and move convoluted, and we perhaps need to
> straighten it.
>
I will update/streamline __alloc_pages code and send the patch.
> It looks like we're now dropping into direct reclaim as the first thing
> in __alloc_pages before even trying to kick off kswapd. When the hell
> did that start? Or is that only meant to trigger if we're already below
> the low watermark level?
>
As Andrew said in the other mail that do_reclaim is never true so the
first reclaim never happens. That also means that we don't look at pcp
for the scenarios when zone has run below the low water mark before
waking kswapd.
> What do we want to do at a higher level?
>
> if (order 0) and (have stuff in the local lists)
> take from local lists
> else if (we're under a little pressure)
> do kswapd reclaim
> else if (we're under a lot of pressure)
> do direct reclaim?
>
> That whole code area seems to have been turned into spagetti, without
> any clear comments.
Agreed.
--
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:[~2005-09-30 1:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 22:01 Seth, Rohit
2005-09-29 22:36 ` Andrew Morton
2005-09-30 1:05 ` Rohit Seth
2005-09-29 22:48 ` Martin J. Bligh
2005-09-29 23:11 ` Andrew Morton
2005-09-30 1:58 ` Rohit Seth
2005-09-30 12:30 ` Martin Hicks
2005-09-30 1:32 ` Rohit Seth [this message]
2005-09-30 1:32 ` Martin J. Bligh
2005-09-29 22:50 ` Dave Hansen
2005-09-30 1:10 ` Rohit Seth
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=1128043933.3735.26.camel@akash.sc.intel.com \
--to=rohit.seth@intel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
/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