From: Matthew Wilcox <willy@infradead.org>
To: Huang Shijie <shijie@os.amperecomputing.com>
Cc: Shijie Huang <shijie@amperemail.onmicrosoft.com>,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, linux-mm@kvack.org,
song.bao.hua@hisilicon.com, linux-kernel@vger.kernel.org,
Frank Wang <zwang@amperecomputing.com>
Subject: Re: Is it possible to implement the per-node page cache for programs/libraries?
Date: Wed, 1 Sep 2021 12:32:27 +0100 [thread overview]
Message-ID: <YS9ky9XiR+JkqSDF@casper.infradead.org> (raw)
In-Reply-To: <YS+NXmDO0yqDEBmD@hsj>
On Wed, Sep 01, 2021 at 02:25:34PM +0000, Huang Shijie wrote:
> On Wed, Sep 01, 2021 at 01:30:45PM +0000, Huang Shijie wrote:
> > On Wed, Sep 01, 2021 at 04:25:01AM +0100, Matthew Wilcox wrote:
> > > On Wed, Sep 01, 2021 at 11:07:41AM +0800, Shijie Huang wrote:
> > > > In the NUMA, we only have one page cache for each file. For the
> > > > program/shared libraries, the
> > > > remote-access delays longer then the local-access.
> > > >
> > > > So, is it possible to implement the per-node page cache for
> > > > programs/libraries?
> > >
> > > At this point, we have no way to support text replication within a
> > > process. So what you're suggesting (if implemented) would work for
> >
> > I created a glibc patch which can do the text replication within a process.
> The "text replication" means the shared libraries, not program itself.
Is it really worthwhile to do only the shared libraries?
next prev parent reply other threads:[~2021-09-01 11:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 3:07 Is it possible to implement the per-node page cache for programs/libraries? Shijie Huang
2021-09-01 2:09 ` Barry Song
2021-09-01 3:25 ` Matthew Wilcox
2021-09-01 13:30 ` Huang Shijie
2021-09-01 14:25 ` Huang Shijie
2021-09-01 11:32 ` Matthew Wilcox [this message]
2021-09-01 23:58 ` Matthew Wilcox
2021-09-02 0:15 ` Barry Song
2021-09-02 1:13 ` Linus Torvalds
2021-09-02 10:16 ` Huang Shijie
2021-09-02 3:25 ` Nicholas Piggin
2021-09-02 10:17 ` Matthew Wilcox
2021-09-03 7:10 ` Nicholas Piggin
2021-09-03 19:01 ` Matthew Wilcox
2021-09-03 19:08 ` Linus Torvalds
2021-09-06 9:56 ` Huang Shijie
2021-09-03 23:42 ` Nicholas Piggin
2021-09-01 4:55 ` Al Viro
2021-09-01 13:10 ` Huang Shijie
2021-09-01 17:24 ` Linus Torvalds
2021-09-01 17:29 ` Linus Torvalds
2021-09-01 22:56 ` Barry Song
2021-09-02 10:12 ` Huang Shijie
2021-09-02 10:08 ` Huang Shijie
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=YS9ky9XiR+JkqSDF@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shijie@amperemail.onmicrosoft.com \
--cc=shijie@os.amperecomputing.com \
--cc=song.bao.hua@hisilicon.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zwang@amperecomputing.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;
as well as URLs for NNTP newsgroup(s).