From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: gerrit@us.ibm.com
Cc: Ben LaHaise <bcrl@redhat.com>,
Chuck Lever <Charles.Lever@netapp.com>,
linux-mm@kvack.org
Subject: Re: 2.5 page cache improvement idea
Date: Tue, 27 Feb 2001 01:21:24 -0800 (PST) [thread overview]
Message-ID: <200102270921.BAA10874@google.engr.sgi.com> (raw)
In-Reply-To: <200102270905.f1R958I03268@eng1.sequent.com> from "Gerrit Huizenga" at Feb 27, 2001 01:05:08 AM
>
>
> That change is platform specific, isn't it? I thought there was also
Yes, completely.
> a recent IA-64 patch in progress for the same thing, but I might
Yes, a couple of people are planning on attempting that soon, we will
see when someone gets to it.
> be mistaken. I'm thinking that it would be useful if the machine
> independent code supported kernel text replication as well as
There *might* be some changes needed for kernel text replication
(mostly to deal with /proc/kcore type of things), but for the most
part, this is really arch specific. You know, those types of things
that tend to show up mostly in production environment, rather than
at the prototype/testing stages.
> shared/read-only text replication for user level applications.
>
User level apps, now thats a different beast. I *suspect* a lot
of work needs to be put into replication heuristics before you can
reap benefits from it. Currently, this is in my pet numa priority list,
but not one of the top few.
Kanoj
> gerrit
>
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-02-27 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 23:46 Ben LaHaise
2001-02-27 0:41 ` Christoph Hellwig
2001-02-27 2:42 ` Chuck Lever
2001-02-27 2:49 ` Ben LaHaise
2001-02-27 3:26 ` Gerrit Huizenga
2001-02-27 5:47 ` Kanoj Sarcar
2001-02-27 9:05 ` Gerrit Huizenga
2001-02-27 9:21 ` Kanoj Sarcar [this message]
2001-02-27 13:42 ` Andrea Arcangeli
2001-02-27 11:52 ` Stephen C. Tweedie
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=200102270921.BAA10874@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=Charles.Lever@netapp.com \
--cc=bcrl@redhat.com \
--cc=gerrit@us.ibm.com \
--cc=linux-mm@kvack.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