All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: sched domains kernbench improvements
Date: Sat, 28 Feb 2004 22:23:00 +1100	[thread overview]
Message-ID: <40407A14.90108@cyberone.com.au> (raw)
In-Reply-To: <200402282218.41590.kernel@kolivas.org>



Con Kolivas wrote:

>On Sat, 28 Feb 2004 22:15, Nick Piggin wrote:
>
>>Con Kolivas wrote:
>>
>>>Hi Nick
>>>
>>>
>>>>So it is more a matter of tuning than anything fundamental
>>>>
>>>Geez I know how you feel... :-D
>>>
>>>
>>>I tried it on the X440 with sched smt disabled
>>>
>>>better than before but still slower than vanilla on half load; however
>>>better than vanilla on optimal and full load now! I wonder whether the
>>>worse result on half load is as relevant since this is 8x HT cpus?
>>>
>>Thanks. Yep the drop off at half load is to be expected with
>>CONFIG_SCHED_SMT turned off.
>>
>
>Will this affect the SCHED_SMT performance and should I do a round of benchies 
>with this enabled?
>
>

It will as far as balancing between physical CPUs, yes. It probably
doesn't make quite a big difference because it is less of a problem
if one sibling goes idle than if one CPU (in the 8-way) goes idle).

But if you could do a round with SCHED_SMT enabled it would be very
nice of you ;)


  reply	other threads:[~2004-02-28 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 10:59 sched domains kernbench improvements Con Kolivas
2004-02-28 11:15 ` Nick Piggin
2004-02-28 11:18   ` Con Kolivas
2004-02-28 11:23     ` Nick Piggin [this message]
2004-02-28 12:27       ` Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2004-02-28  9:21 Nick Piggin

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=40407A14.90108@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.