From: Andrew Morton <akpm@digeo.com>
To: Dave McCracken <dmccr@us.ibm.com>,
Linux Scalability Effort List <lse-tech@lists.sourceforge.net>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [Lse-tech] Rollup patch of basic rmap against 2.5.26
Date: Tue, 17 Sep 2002 14:17:05 -0700 [thread overview]
Message-ID: <3D879BD1.D02F645E@digeo.com> (raw)
In-Reply-To: <3D879968.B346D1C7@digeo.com>
Andrew Morton wrote:
>
> Dave McCracken wrote:
> >
> > ...
> > daniel_rmap_speedup Use hashed pte_chain locks
>
> This one was shown to be a net loss on the NUMA-Q's.
>
But thanks for testing - I forgot to say that ;)
rmap's overhead manifests with workloads which are setting
up and tearing doen pagetables a lot.
fork/exec/exit/pagefaults/munmap/etc. I guess forking servers
may hurt.
--
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/
next prev parent reply other threads:[~2002-09-17 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 18:21 Dave McCracken
2002-09-17 21:06 ` [Lse-tech] " Andrew Morton
2002-09-17 21:17 ` Andrew Morton [this message]
2002-09-19 11:07 ` Ingo Oeser
2002-09-17 20:44 Partha Narayanan
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=3D879BD1.D02F645E@digeo.com \
--to=akpm@digeo.com \
--cc=dmccr@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
/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