public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bru <xavier.bru@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] top level scheduler domain for ia64
Date: Thu, 21 Oct 2004 14:11:48 +0000	[thread overview]
Message-ID: <4177C3A4.8080207@bull.net> (raw)
In-Reply-To: <200410191427.27336.jbarnes@engr.sgi.com>

Hello Nick & all,

Nick Piggin wrote:

> Luck, Tony wrote:
>
>
>> +    .min_interval        = 80,            \
>> +    .max_interval        = 320,            \
>> +    .busy_factor        = 320,            \
>> +    .imbalance_pct        = 125,            \
>> +    .cache_hot_time        = (10*1000000),        \
>> +    .balance_interval    = 100*(63+num_online_cpus())/64,   \
>>
>> That's a lot of magic numbers and formulae ... are they right?
>> How would a user know if they are right.
>>
>
> To be honest you really wouldn't. It would take a lot of careful
> testing on numerous workloads and systems. I believe SGI is
> starting to do a bit of testing... I don't have the resources to
> do many "real world" tests.
>
> At this stage I wouldn't let them worry you too much :P
> Hopefully they'll gradually improve.

Why should'nt we use the node_distance() function to build in an 
independant way the Numa hierarchy and compute the right parameters for 
each level ?


-- 

 Sincères salutations.
_____________________________________________________________________
 
Xavier BRU                 BULL ISD/R&D/INTEL office:     FREC B1-422
tel : +33 (0)4 76 29 77 45                    http://www-frec.bull.fr
fax : +33 (0)4 76 29 77 70                 mailto:Xavier.Bru@bull.net
addr: BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, FRANCE
_____________________________________________________________________



  parent reply	other threads:[~2004-10-21 14:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 21:27 [PATCH] top level scheduler domain for ia64 Jesse Barnes
2004-10-20  0:02 ` Nick Piggin
2004-10-20 17:48 ` Luck, Tony
2004-10-20 18:02 ` Nick Piggin
2004-10-20 18:03 ` Jesse Barnes
2004-10-21 14:11 ` Xavier Bru [this message]
2004-10-21 14:34 ` Nick Piggin
2004-10-28  9:29 ` Takayoshi Kochi
2004-10-28 15:26 ` Jesse Barnes
2004-11-01  6:35 ` Takayoshi Kochi
2004-11-01 17:07 ` Jesse Barnes
2004-11-01 17:16 ` Matthew Wilcox
2004-11-01 18:36 ` Jesse Barnes
2004-11-01 18:53 ` Luck, Tony
2004-11-01 19:02 ` Jesse Barnes
2004-11-01 19:45 ` Luck, Tony
2004-11-01 22:39 ` Jesse Barnes
2004-11-02  0:12 ` Zou, Nanhai
2004-11-02  7:36 ` Takayoshi Kochi
2004-11-02  8:48 ` Gerald Pfeifer
2004-11-02  9:31 ` Takayoshi Kochi
2004-11-02 21:31 ` Luck, Tony
2004-11-03  6:15 ` Takayoshi Kochi
2004-11-03 16:22 ` Jesse Barnes
2004-11-03 16:57 ` Luck, Tony
2004-11-03 17:04 ` Jesse Barnes
2004-11-08 17:31 ` John Hawkes

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=4177C3A4.8080207@bull.net \
    --to=xavier.bru@bull.net \
    --cc=linux-ia64@vger.kernel.org \
    /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