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: Mon, 26 Feb 2001 21:47:25 -0800 (PST) [thread overview]
Message-ID: <200102270547.VAA94414@google.engr.sgi.com> (raw)
In-Reply-To: <200102270326.f1R3QII16835@eng1.sequent.com> from "Gerrit Huizenga" at Feb 26, 2001 07:26:18 PM
> node traffic is relatively expensive. As a result, wasting a small
> number of physical pages on duplicate read-only pages cuts down node
> to node traffic in most cases. Many NUMA systems have a cache for
> remote memory (some cache only remote pages, some cache local and remote
> pages in the same cache - icky but cheaper). As that cache cycles,
> it is cheaper to replace read-only text pages from the local node
> rather than the remote. So, for things like kernel text (e.g. one of
> the SGI patches) and for glibc's text, as well as the text of other
The mips64 port onto SGI o2000 uses kernel text replication, that has
been part of 2.3/2.4 for a long time now. Is there another patch you
are talking about here?
Kanoj
--
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 5:47 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 [this message]
2001-02-27 9:05 ` Gerrit Huizenga
2001-02-27 9:21 ` Kanoj Sarcar
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=200102270547.VAA94414@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