From: Martin Hicks <mort@wildopensource.com>
To: Andrew Morton <akpm@osdl.org>
Cc: rusty@rustcorp.com.au, steiner@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Reduce TLB flushing during process migration
Date: Tue, 17 Feb 2004 17:01:54 -0500 [thread overview]
Message-ID: <20040217220154.GT12142@localhost> (raw)
In-Reply-To: <20040217125038.14396a1d.akpm@osdl.org>
On Tue, Feb 17, 2004 at 12:50:38PM -0800, Andrew Morton wrote:
> Martin Hicks <mort@wildopensource.com> wrote:
> >
> > Another optimization patch from Jack Steiner, intended to reduce TLB
> > flushes during process migration.
>
> This patch is only applicable to CONFIG_NUMA. Wouldn't SMP systems benefit
> from the same treatment?
>
> And does this optimisation come with any benchmark results?
Here's some figures from Jack:
---
I dont have a benchmark for JUST the scheduler change, but the entire
node history + sched change is:
nwchem on a 128p showed:
Before:
siosi7.sale.56-shm1cs: Time after atomic energies summed: 140.2
siosi7.sale.120-shm1cs: Time after atomic energies summed: 306.9
After:
56p = Time after atomic energies summed: 99.3
120p = Time after atomic energies summed: 110.4
Almost 3X improvement on 120p.
I dont recall how much was due to the sched fix, but I remember that it was
significant.
Note that the amount of improvement is highly platform specific.
---
mh
--
Martin Hicks Wild Open Source Inc.
mort@wildopensource.com 613-266-2296
next prev parent reply other threads:[~2004-02-17 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 15:49 [PATCH] Reduce TLB flushing during process migration Martin Hicks
2004-02-17 18:07 ` David S. Miller
2004-02-17 20:50 ` Andrew Morton
2004-02-17 22:01 ` Martin Hicks [this message]
2004-02-18 2:34 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 16:22 Manfred Spraul
2004-02-17 18:08 ` David S. Miller
2004-02-17 20:05 ` Martin Hicks
2004-02-17 20:08 ` David S. Miller
2004-02-17 20:37 ` Martin Hicks
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=20040217220154.GT12142@localhost \
--to=mort@wildopensource.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=steiner@sgi.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