From: Ingo Molnar <mingo@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Nick Piggin <piggin@cyberone.com.au>,
Joe Pranevich <jpranevich@kniggit.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wonderful World of Linux 2.6 - Final
Date: Thu, 18 Dec 2003 03:16:25 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0312180314330.17551@devserv.devel.redhat.com> (raw)
In-Reply-To: <3FE1532A.2010109@pobox.com>
On Thu, 18 Dec 2003, Jeff Garzik wrote:
> Are you sure? I could have sworn Ingo made the scheduler magically
> HT-friendly...
nope, it's not in 2.6 yet. This area is still under development, with
various approaches being considered.
Ingo
next prev parent reply other threads:[~2003-12-18 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 5:37 Wonderful World of Linux 2.6 - Final Nick Piggin
2003-12-18 7:11 ` Jeff Garzik
2003-12-18 8:16 ` Ingo Molnar [this message]
2003-12-18 12:21 ` Joe Pranevich
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 7:49 Nakajima, Jun
2003-12-18 5:13 Joe Pranevich
2003-12-18 15:29 ` Andrew Theurer
2003-12-18 15:35 ` Andrew Theurer
2003-12-18 23:52 ` Andrea Arcangeli
2003-12-18 23:58 ` Andrew Theurer
2003-12-19 0:03 ` Andrea Arcangeli
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=Pine.LNX.4.58.0312180314330.17551@devserv.devel.redhat.com \
--to=mingo@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jpranevich@kniggit.net \
--cc=linux-kernel@vger.kernel.org \
--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