public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: Erich Focht <focht@ess.nec.de>
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Node affine NUMA scheduler
Date: Thu, 14 Mar 2002 09:28:08 -0800	[thread overview]
Message-ID: <20020314172808.GB138234@sgi.com> (raw)
In-Reply-To: <20020314025818.GA136486@sgi.com> <Pine.LNX.4.21.0203141459260.12844-100000@sx6.ess.nec.de>
In-Reply-To: <Pine.LNX.4.21.0203141459260.12844-100000@sx6.ess.nec.de>

On Thu, Mar 14, 2002 at 03:54:12PM +0100, Erich Focht wrote:
> Jesse,
> 
> thanks for running the tests. Actually "hackbench" is a bad example for
> the node affinity (though it's a good test for heavy scheduling). The code
> forks but doesn't exec and therefore all hackbench tasks have the same
> homenode. Also the tasks are not particularly memory bandwidth or latency
> hungry, therefore node affinity won't speed them up. I'm actually glad
> that they aren't slower, that shows that the additional overhead is small.

Alright, I'll try running some other numbers too, what can you
recommend other than aim and kernel compiles?

> Thanks for sending the macros for SGI_SN1/2, I'll include them. You
> probably use the DISCONTIGMEM patch, for that I append a small patch which
> "couples" DISCONTIGEMEM with the node affine scheduler such that pages
> will be allocated on the node current->node instead of the node on which
> the task is currently running. Hackbench might slow down a bit but
> AIM7 should improve.

Sounds good, I'll have to update those macros later too (Jack
reminded me that physical node numbers aren't always the same as
logical node numbers).

Jesse

  parent reply	other threads:[~2002-03-14 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 20:10 Node affine NUMA scheduler Erich Focht
2002-03-14  2:58 ` Jesse Barnes
2002-03-14 14:54   ` Erich Focht
2002-03-14 16:11     ` Erich Focht
2002-03-14 20:00       ` [Lse-tech] " Gerrit Huizenga
2002-03-15  2:03         ` Erich Focht
2002-03-14 17:28     ` Jesse Barnes [this message]
2002-03-15  1:57       ` Erich Focht
     [not found] <mailman.1016050377.26216.linux-kernel2news@redhat.com>
2002-03-13 20:38 ` Pete Zaitcev
  -- strict thread matches above, loose matches on Subject: below --
2002-07-22 13:59 node " Erich Focht

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=20020314172808.GB138234@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=focht@ess.nec.de \
    --cc=linux-kernel@vger.kernel.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