public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Nick Piggin <piggin@cyberone.com.au>
Subject: Re: [PATCH] 2.6.1 Hyperthread smart "nice" 2
Date: Tue, 3 Feb 2004 22:14:49 +1100	[thread overview]
Message-ID: <200402032214.49229.kernel@kolivas.org> (raw)
In-Reply-To: <20040203111236.GA8508@elte.hu>

On Tue, 3 Feb 2004 22:12, Ingo Molnar wrote:
> * Con Kolivas <kernel@kolivas.org> wrote:
> > > for lowprio tasks they are of little use, unless you modify gcc to
> > > sprinkle mwait yields all around the 'lowprio code' - not very
> > > practical i think.
> >
> > Yuck!
> >
> > Looks like the kernel is the only thing likely to be smart enough to
> > do this correctly for some time yet.
>
> no, there's no way for the kernel to do this 'correctly', without
> further hardware help. mwait is suspending the current virtual CPU a bit
> better than rep-nop did. This can be exploited for the idle loop because
> the idle loop does nothing so it can execute the rep-nop. (mwait can
> likely also be used for spinlocks but that is another issue.)
>
> user-space code that is 'low-prio' cannot be slowed down via mwait,
> without interleaving user-space instructions with mwait (or with
> rep-nop).
>
> this is a problem area that is not solved by mwait - giving priority to
> virtual CPUs should be offered by CPUs, once the number of logical cores
> increases significantly - if the interaction between those cores is
> significant. (there are SMT designs where this isnt an issue.)

Actually I was trying to say something like my patch, but done correctly. I 
agree with new instructions not helping at the moment.

Con

  reply	other threads:[~2004-02-03 11:15 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
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 [this message]
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=200402032214.49229.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=piggin@cyberone.com.au \
    /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