From: Jos Hulzink <josh@stack.nl>
To: Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.1 Hyperthread smart "nice"
Date: Thu, 29 Jan 2004 10:39:22 +0100 [thread overview]
Message-ID: <200401291039.22561.josh@stack.nl> (raw)
In-Reply-To: <200401291917.42087.kernel@kolivas.org>
On Thursday 29 Jan 2004 09:17, Con Kolivas wrote:
> Hi all
>
> This patch (together with the ht base patch) will not allow a priority >10
> difference to run concurrently on both siblings, instead putting the low
> priority one to sleep. Overall if you run concurrent nice 0 and nice 20
> tasks with this patch your cpu throughput will drop during heavy periods by
> up to 10% (the hyperthread benefit), but your nice 0 task will run about
> 90% faster. It has no effect if you don't run any tasks at different "nice"
> levels. It does not modify real time tasks or kernel threads, and will
> allow niced tasks to run while a high priority kernel thread is running on
> the sibling cpu.
If I read you correctly, if one thread has nothing else to do but the nice 0
task, the nice 20 task will never be scheduled at all ? Sounds like not the
perfect solution to me...
Jos
next prev parent reply other threads:[~2004-01-29 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 8:17 [PATCH] 2.6.1 Hyperthread smart "nice" Con Kolivas
2004-01-29 9:39 ` Jos Hulzink [this message]
2004-01-29 10:28 ` Con Kolivas
2004-01-29 10:36 ` Con Kolivas
2004-02-02 9:27 ` [PATCH] 2.6.1 Hyperthread smart "nice" 2 Con Kolivas
2004-02-02 10:31 ` Ingo Molnar
2004-02-03 10:52 ` Con Kolivas
2004-02-03 10:58 ` Ingo Molnar
2004-02-03 11:07 ` Con Kolivas
2004-02-03 11:12 ` Ingo Molnar
2004-02-03 11:14 ` Con Kolivas
2004-02-03 11:47 ` Ingo Molnar
2004-02-03 11:19 ` Nick Piggin
2004-02-03 22:59 ` Andrew Morton
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=200401291039.22561.josh@stack.nl \
--to=josh@stack.nl \
--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