From: Ray Bryant <raybry@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Ray Bryant <raybry@austin.rr.com>,
William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@osdl.org>, linux-mm <linux-mm@kvack.org>,
Jesse Barnes <jbarnes@sgi.com>, Dan Higgins <djh@sgi.com>,
Dave Hansen <haveblue@us.ibm.com>,
lse-tech <lse-tech@lists.sourceforge.net>,
Brent Casavant <bcasavan@sgi.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Paul Jackson <pj@sgi.com>, Nick Piggin <piggin@cyberone.com.au>
Subject: Re: [PATCH 1/2] mm: page cache mempolicy for page cache allocation
Date: Thu, 23 Sep 2004 23:12:49 -0500 [thread overview]
Message-ID: <41539EC1.1040301@sgi.com> (raw)
In-Reply-To: <20040923092416.GC6146@wotan.suse.de>
Andi Kleen wrote:
>
> Overall when I look at all the complications you add for the per process
> page policy which doesn't even have a demonstrated need I'm not sure
> it is really worth it.
>
Polling people inside of SGI, they seem to think that a per file memory policy
is a good thing, but it needs to be settable from outside the process without
changing the header or code of the process (think of an ISV application that
we want to run on Altix.) I can't quite get my head around what that means
(do you have to specify this externally based on the order that files are
opened in [e. g. file 1 has policy this, file 2 has policy that, etc] or does
one specify this by type of file [text, mapped file, etc]). Does this end up
being effectively a per process policy with a per file override? (e. g. all
files for this process are managed with policy "this", except for the 5th file
opened [or whatever] and it has policy "that".)
Steve -- how does your MTA design handle this?
Anyway, I'm about to throw in the towel on the per process page cache memory
policy. I can't make a strong enough argument for it.
I assume that is acceptable, Andi? :-)
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
--
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>
next prev parent reply other threads:[~2004-09-24 4:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 4:32 [PATCH 0/2] mm: memory policy " 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 [this message]
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 ` [PATCH 0/2] mm: memory policy for page cache allocation Andi Kleen
2004-09-23 18:56 [PATCH 1/2] mm: page cache mempolicy " Ray Bryant
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=41539EC1.1040301@sgi.com \
--to=raybry@sgi.com \
--cc=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=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