mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erich Focht <efocht@ess.nec.de>
To: Andrew Theurer <habanero@us.ibm.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	Michael Hohnbaum <hohnbaum@us.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pooling NUMA scheduler with initial load balancing
Date: Fri, 11 Oct 2002 10:27:59 +0200	[thread overview]
Message-ID: <200210111027.59589.efocht@ess.nec.de> (raw)
In-Reply-To: <200210110947.11714.efocht@ess.nec.de>

On Friday 11 October 2002 09:47, Erich Focht wrote:
> Hi Andrew,
>
> On Thursday 10 October 2002 19:34, Andrew Theurer wrote:
> > Thanks very much Erich.  I did come across another problem here on
> > numa-q. In task_to_steal() there is a divide by cache_decay_ticks, which
> > apparantly is 0 on my system.  This may have to do with notsc, but I am
> > not sure.  I set cache_decay_ticks to 8, (I cannot boot without using
> > notsc) which is probably not correct, but I can now boot 16 processor
> > numa-q on 2.5.40-mm1 with your patches!  I'll get some benchmark results
> > soon.
>
> oops... This is a bug in 2.5-i386. It means that the O(1) scheduler in
> 2.5 doesn't work well either because it doesn't take into account cache
> coolness. I'll post a fix to LKML in a few minutes.

Sorry, I thought the smp_tune_scheduling() call went lost during the
transition to the new cpu boot scheme. But it's there. And the problem
is indeed "notsc". So you'll have to fix it, I can't.

If you set the cache_decay_ticks to something non-zero, you should
_really_ do this for all the scheduler tests, otherwise your measurements
will not be comparable.

Regards,
Erich


  parent reply	other threads:[~2002-10-11  8:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06 16:51 [RFC] NUMA schedulers benchmark results Erich Focht
2002-10-06 20:24 ` Erich Focht
2002-10-07  0:00   ` Martin J. Bligh
2002-10-07  0:58 ` Martin J. Bligh
2002-10-07 16:52   ` Erich Focht
2002-10-07  7:25 ` Martin J. Bligh
2002-10-07  7:40   ` Ingo Molnar
2002-10-07 20:09   ` [PATCH] pooling NUMA scheduler with initial load balancing Erich Focht
     [not found]     ` <1420721189.1034032091@[10.10.2.3]>
2002-10-08 17:33       ` Erich Focht
2002-10-08 19:44         ` Martin J. Bligh
2002-10-09 16:26           ` Erich Focht
2002-10-09 17:33             ` Martin J. Bligh
2002-10-09 17:58               ` Andrew Theurer
2002-10-09 18:13                 ` Andrew Theurer
2002-10-09 23:02                 ` Erich Focht
2002-10-10 17:34                   ` Andrew Theurer
     [not found]                     ` <200210110947.11714.efocht@ess.nec.de>
2002-10-11  8:27                       ` Erich Focht [this message]
2002-10-11 14:47                         ` Martin J. Bligh
2002-10-11 15:29                           ` Erich Focht
2002-10-11 15:34                             ` Martin J. Bligh
2002-10-09  1:15         ` Christoph Hellwig
2002-10-09 10:29           ` Erich Focht
2002-10-07 16:37 ` [RFC] NUMA schedulers benchmark results Michael Hohnbaum
2002-10-07 20:35   ` 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=200210111027.59589.efocht@ess.nec.de \
    --to=efocht@ess.nec.de \
    --cc=habanero@us.ibm.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --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

all inboxes | Powered by JetHome®