From: Andi Kleen <ak@suse.de>
To: Ray Bryant <raybry@austin.rr.com>
Cc: Andi Kleen <ak@suse.de>,
William Lee Irwin III <wli@holomorphy.com>,
linux-mm <linux-mm@kvack.org>, Jesse Barnes <jbarnes@sgi.com>,
Dan Higgins <djh@sgi.com>,
lse-tech <lse-tech@lists.sourceforge.net>,
Brent Casavant <bcasavan@sgi.com>,
Nick Piggin <piggin@cyberone.com.au>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ray Bryant <raybry@sgi.com>, Andrew Morton <akpm@osdl.org>,
Paul Jackson <pj@sgi.com>, Dave Hansen <haveblue@us.ibm.com>
Subject: Re: [PATCH 0/2] mm: memory policy for page cache allocation
Date: Thu, 23 Sep 2004 11:09:58 +0200 [thread overview]
Message-ID: <20040923090957.GB6146@wotan.suse.de> (raw)
In-Reply-To: <20040923043236.2132.2385.23158@raybryhome.rayhome.net>
> (1) We dropped the MPOL_ROUNDROBIN patch. Instead, we
> use MPOL_INTERLEAVE to spread pages across nodes.
> However, rather than use the file offset etc to
> calculate the node to allocate the page on, I used
> the same mechanism you used in alloc_pages_current()
> to calculate the node number (interleave_node()).
> That eliminates the need to generate an offset etc
> in the routines that call page_cache_alloc() and to
> me appears to be a simpler change that still fits
> within your design.
Hmm, that may lead to uneven balancing because the counter is
per thread. But if it works for you it's ok I guess.
I still think changing the callers and use the offset for
static interleaving would be better. Maybe that could be
done as a followon patch.
>
> (2) I implemented the sys_set_mempolicy() changes as
> suggested -- higher order bits in the mode (first)
> argument specify whether or not this request is for
> the page allocation policy (your existing policy)
> or for the page cache allocation policy. Similarly,
> a bit there indicates whether or not we want to set
> the process level policy or the system level policy.
>
> These bits are to be set in the flags argument of
> sys_mbind().
Ok. If that gets in I would suggest you also document it
in the manpages and send me a patch.
Comments to the patches in other mail.
-Andi
next prev parent reply other threads:[~2004-09-23 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 4:32 Ray Bryant
2004-09-23 4:32 ` [PATCH 1/2] mm: page cache mempolicy " Ray Bryant
2004-09-23 9:24 ` Andi Kleen
2004-09-24 4:12 ` Ray Bryant
2004-09-23 4:32 ` [PATCH 2/2] mm: eliminate node 0 bias in MPOL_INTERLEAVE Ray Bryant
2004-09-23 9:29 ` Andi Kleen
2004-09-24 6:33 ` Ray Bryant
2004-09-24 6:43 ` Ray Bryant
2004-09-23 9:09 ` Andi Kleen [this message]
[not found] <fa.b014hh3.12l6193@ifi.uio.no>
[not found] ` <fa.ep2m52m.1p0edrq@ifi.uio.no>
2004-09-24 15:43 ` [PATCH 0/2] mm: memory policy for page cache allocation Ray Bryant
2004-09-25 5:40 ` Steve Longerbeam
-- strict thread matches above, loose matches on Subject: below --
2004-09-20 19:00 [PATCH 2.6.9-rc2-mm1 " Ray Bryant
2004-09-20 20:55 ` Andi Kleen
2004-09-20 23:48 ` Steve Longerbeam
2004-09-23 15:54 ` [PATCH " Ray Bryant
2004-09-23 23:01 ` Steve Longerbeam
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=20040923090957.GB6146@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bcasavan@sgi.com \
--cc=djh@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=piggin@cyberone.com.au \
--cc=pj@sgi.com \
--cc=raybry@austin.rr.com \
--cc=raybry@sgi.com \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®