From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] SMT Nice 2.6.4-rc1-mm1
Date: Mon, 01 Mar 2004 22:46:02 +1100 [thread overview]
Message-ID: <4043227A.6050806@cyberone.com.au> (raw)
In-Reply-To: <200403012240.34535.kernel@kolivas.org>
Con Kolivas wrote:
>On Mon, 1 Mar 2004 10:37 pm, Nick Piggin wrote:
>
>>Con Kolivas wrote:
>>
>>>On Mon, 1 Mar 2004 05:52 pm, Con Kolivas wrote:
>>>
>>>>This patch provides full per-package priority support for SMT processors
>>>>(aka pentium4 hyperthreading) when combined with CONFIG_SCHED_SMT.
>>>>
>>>And here are some benchmarks to demonstrate what happens.
>>>P4 3.06Ghz booted with bios HT off as UP (up), SMP with mm1(mm1), SMP with
>>>mm1-smtnice(sn)
>>>
>>Pretty impressive numbers.
>>
>>How does it go on the desktop when running mprime at nice +19?
>>How much worse can latencies of the niced tasks become? Any idea?
>>
>
>Worst case scenario is easy to model; if a nice -19 task starts at exactly the
>same time as a nice +19 task, the timeslices are 200 and 10ms. On
>uniprocessor the nice+19 task will wait _at least_ 200 ms. On SMT nice SMP it
>will be 200 - (200 * 15 / 100) so 170ms. That is of course worst case
>scenario and still better than UP since the latency will be less, the task
>will definitely start (interactive reinsertion wont affect it) and it will be
>on a second runqueue.
>
>
OK thats good. I'm still not exactly how to generalise the cpu power
/ impact stuff, but that isn't critical. It should be done some time
though.
I'd be happy to see this patch in -mm. As Con mentioned, it would be
probably good to merge it one major release after base sched domains
is merged (if ever).
Thanks Con.
next prev parent reply other threads:[~2004-03-01 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 6:52 [PATCH] SMT Nice 2.6.4-rc1-mm1 Con Kolivas
2004-03-01 11:25 ` Con Kolivas
2004-03-01 11:37 ` Nick Piggin
2004-03-01 11:40 ` Con Kolivas
2004-03-01 11:46 ` Nick Piggin [this message]
2004-03-01 11:53 ` Con Kolivas
2004-03-01 11:45 ` Con Kolivas
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=4043227A.6050806@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox