From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Mel <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page_alloc.c comments patch v2
Date: Thu, 18 Apr 2002 18:54:02 -0700 [thread overview]
Message-ID: <1940570000.1019181242@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0204190127080.8173-100000@skynet>
> I got confused when I was examining the code and got mixed up. I see now
> the question about more that one ZONE_NORMAL in this pgdata_t is off, but
> the query still (sortof) holds. Let me try again.
>
> I am an allocator and I start in HIGHMEM which has a pages_low value of 10
> (arbitary number). I find I would hit it if I allocated from there so I
> move to NORMAL which also has a pages_low of 10 but now I am making sure I
> am at least 20 pages are free in the NORMAL zone, not 10 and possibly
> (presuming pages_low in DMA is 10) making sure 30 are free in DMA. Is this
> the way things are meant to happen?
Ah, OK, I see what you were getting at now ;-)
It's hard to really tell what was intended - Andrea might be able to give
you a
better idea. However, from the way I read the code, it might seem to make
more
sense if the "min = 1UL << order;" was inside the loop rather than outside.
That'd simply make sure we always left "zone->pages_low" free inside that
zone .... if course it would make no sense to assign min and then increment
it
with += inside the loop, or even set it any more .... just
if (z->free_pages > z->pages_low + (1UL << order))
But all that's purely speculation, he might have meant it as it is ;-)
M.
prev parent reply other threads:[~2002-04-19 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 23:16 page_alloc.c comments patch v2 Mel
2002-04-19 1:17 ` Martin J. Bligh
2002-04-19 0:37 ` Mel
2002-04-19 1:54 ` Martin J. Bligh [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=1940570000.1019181242@flay \
--to=martin.bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.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