From: Nick Piggin <npiggin@suse.de>
To: Martin Bligh <mbligh@mbligh.org>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Eric Whitney <eric.whitney@hp.com>
Subject: Re: [rfc] balance-on-fork NUMA placement
Date: Fri, 3 Aug 2007 02:20:10 +0200 [thread overview]
Message-ID: <20070803002010.GB14775@wotan.suse.de> (raw)
In-Reply-To: <46B22383.5020109@mbligh.org>
On Thu, Aug 02, 2007 at 11:33:39AM -0700, Martin Bligh wrote:
> Nick Piggin wrote:
> >On Wed, Aug 01, 2007 at 03:52:11PM -0700, Martin Bligh wrote:
> >>>And so forth. Initial forks will balance. If the children refuse to
> >>>die, forks will continue to balance. If the parent starts seeing short
> >>>lived children, fork()s will eventually start to stay local.
> >>Fork without exec is much more rare than without. Optimising for
> >>the uncommon case is the Wrong Thing to Do (tm). What we decided
> >
> >It's only the wrong thing to do if it hurts the common case too
> >much. Considering we _already_ balance on exec, then adding another
> >balance on fork is not going to introduce some order of magnitude
> >problem -- at worst it would be 2x but it really isn't too slow
> >anyway (at least nobody complained when we added it).
> >
> >One place where we found it helps is clone for threads.
> >
> >If we didn't do such a bad job at keeping tasks together with their
> >local memory, then we might indeed reduce some of the balance-on-crap
> >and increase the aggressiveness of periodic balancing.
> >
> >Considering we _already_ balance on fork/clone, I don't know what
> >your argument is against this patch is? Doing the balance earlier
> >and allocating more stuff on the local node is surely not a bad
> >idea.
>
> I don't know who turned that on ;-( I suspect nobody bothered
> actually measuring it at the time though, or used some crap
> benchmark like stream to do so. It should get reverted.
So you have numbers to show it hurts? I tested some things where it
is not supposed to help, and it didn't make any difference. Nobody
else noticed either.
If the cost of doing the double balance is _really_ that painful,
then we ccould skip balance-on-exec for domains with balance-on-fork
set.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-08-03 0:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 5:41 Nick Piggin
2007-07-31 8:01 ` Ingo Molnar
2007-08-01 0:21 ` Nick Piggin
2007-08-01 6:19 ` Ingo Molnar
2007-07-31 9:14 ` Andi Kleen
2007-07-31 23:40 ` Christoph Lameter
2007-08-01 8:39 ` Andi Kleen
2007-08-02 3:42 ` Nick Piggin
2007-08-02 19:58 ` Christoph Lameter
2007-08-03 0:26 ` Nick Piggin
2007-08-03 0:52 ` Christoph Lameter
2007-08-03 0:57 ` Nick Piggin
2007-08-03 1:02 ` Christoph Lameter
2007-08-03 1:14 ` Nick Piggin
2007-08-03 1:34 ` Christoph Lameter
2007-08-03 3:14 ` Nick Piggin
2007-08-03 5:47 ` Christoph Lameter
2007-08-01 0:23 ` Nick Piggin
2007-08-01 17:53 ` Martin Bligh
2007-08-01 18:32 ` Lee Schermerhorn
2007-08-01 22:52 ` Martin Bligh
2007-08-02 1:36 ` Nick Piggin
2007-08-02 18:33 ` Martin Bligh
2007-08-03 0:20 ` Nick Piggin [this message]
2007-08-03 20:10 ` Siddha, Suresh B
2007-08-06 1:20 ` Nick Piggin
2007-08-02 14:49 ` Lee Schermerhorn
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=20070803002010.GB14775@wotan.suse.de \
--to=npiggin@suse.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=eric.whitney@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=mingo@elte.hu \
/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