From: Jeff Dike <jdike@karaya.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: The O(1) scheduler breaks UML
Date: Sun, 13 Jan 2002 23:49:16 -0500 [thread overview]
Message-ID: <200201140449.XAA06402@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sun, 13 Jan 2002 18:55:35 PST." <Pine.LNX.4.40.0201131853550.937-100000@blue1.dev.mcafeelabs.com>
davidel@xmailserver.org said:
> Yes, this should work :
> if (likely(prev != next)) {
> rq->nr_switches++;
> rq->curr = next;
> next->cpu = prev->cpu;
> spin_unlock_irq(&rq->lock);
> context_switch(prev, next);
> } else
> spin_unlock_irq(&rq->lock);
> and there's no need for barrier() and rq reload in this way.
Yup, UML works much better with that.
Jeff
next prev parent reply other threads:[~2002-01-14 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 2:39 The O(1) scheduler breaks UML Jeff Dike
2002-01-14 2:55 ` Davide Libenzi
2002-01-14 4:49 ` Jeff Dike [this message]
2002-01-14 9:55 ` Ingo Molnar
2002-01-14 15:38 ` Davide Libenzi
2002-01-14 9:40 ` Ingo Molnar
2002-01-14 19:14 ` Jeff Dike
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=200201140449.XAA06402@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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