From: Victor Yodaiken <yodaiken@fsmlabs.com>
To: Hubertus Franke <frankeh@us.ibm.com>
Cc: Victor Yodaiken <yodaiken@fsmlabs.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Scalable Scheduling
Date: Wed, 8 Aug 2001 13:51:43 -0600 [thread overview]
Message-ID: <20010808135143.A8426@hq2> (raw)
In-Reply-To: <OF320F8ECC.3EB12A09-ON85256AA2.006BF096@pok.ibm.com>
On Wed, Aug 08, 2001 at 03:40:00PM -0400, Hubertus Franke wrote:
>
> We did not modify the UP code at all. There will be NO effects (positive
> nor negative) what so ever.
Cool. So the obvious next question is
How does it compare on a dual to the current Linux scheduler?
Obviously:
Performance sucks on two processors but scales well
would not be a good thing.
>
> Hubertus Franke
> Enterprise Linux Group (Mgr), Linux Technology Center (Member Scalability)
> , OS-PIC (Chair)
> email: frankeh@us.ibm.com
> (w) 914-945-2003 (fax) 914-945-4425 TL: 862-2003
>
>
>
> Victor Yodaiken <yodaiken@fsmlabs.com> on 08/08/2001 03:27:55 PM
>
> To: Mike Kravetz <mkravetz@sequent.com>
> cc: Linus Torvalds <torvalds@transmeta.com>, Hubertus
> Franke/Watson/IBM@IBMUS, linux-kernel@vger.kernel.org
> Subject: Re: [RFC][PATCH] Scalable Scheduling
>
>
>
> On Wed, Aug 08, 2001 at 11:28:00AM -0700, Mike Kravetz wrote:
> > One challenge will be maintaining the same level of performance
> > for UP as in the current code. The current code has #ifdefs to
>
> How does the "current code" compare to the current Linux UP code?
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-08-08 19:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 19:40 [RFC][PATCH] Scalable Scheduling Hubertus Franke
2001-08-08 19:51 ` Victor Yodaiken [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 14:22 Erik Corry
2001-08-11 0:04 Hubertus Franke
2001-08-08 20:02 Hubertus Franke
2001-08-08 19:16 Hubertus Franke
2001-08-08 19:05 Hubertus Franke
2001-08-08 17:32 Hubertus Franke
2001-08-08 17:43 ` Linus Torvalds
2001-08-08 18:00 ` Linus Torvalds
2001-08-08 18:18 ` Larry McVoy
2001-08-08 18:53 ` David S. Miller
2001-08-10 23:58 ` Chris Wedgwood
2001-08-08 18:28 ` Mike Kravetz
2001-08-08 19:06 ` Daniel Phillips
2001-08-08 19:14 ` Linus Torvalds
2001-08-08 19:27 ` Victor Yodaiken
2001-08-08 16:16 Mike Kravetz
2001-08-08 16:40 ` Linus Torvalds
2001-08-08 17:05 ` Mike Kravetz
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=20010808135143.A8426@hq2 \
--to=yodaiken@fsmlabs.com \
--cc=frankeh@us.ibm.com \
--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