From: "michael chang" <thenewme91@gmail.com>
To: "Willy Tarreau" <w@1wt.eu>
Cc: "Con Kolivas" <kernel@kolivas.org>,
ck@vds.kolivas.org, "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [ck] Re: RSDL v0.30 cpu scheduler for mainline kernels
Date: Tue, 13 Mar 2007 09:10:27 -0400 [thread overview]
Message-ID: <b14e81f00703130610r409290cex39e9bfa340f7dcbd@mail.gmail.com> (raw)
In-Reply-To: <20070313043206.GN943@1wt.eu>
On 3/13/07, Willy Tarreau <w@1wt.eu> wrote:
> On Tue, Mar 13, 2007 at 02:05:23PM +1100, Con Kolivas wrote:
> > On Tuesday 13 March 2007 10:46, David Miller wrote:
> > > From: Con Kolivas <kernel@kolivas.org>
> > > Date: Mon, 12 Mar 2007 10:58:11 +1100
> > >
> > > > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc3-sched-rsdl-0.
> > > >30.patch
> > >
> > > FWIW, this boots and seems to work well on sparc64. Tested
> > > on UP SunBlade1500 and 24cpu Niagara T1000.
> >
> > Very nice. Thanks for the feedback and I'm sorry you have to work with such
> > lousy hardware.
>
> BTW, I don't know if you say this as a joke, but those are not necessarily
> lousy hardware. Sun does lousy hardware when they put Sparcs in PCs (ultra5,
> ultra10, blade100). But their servers generally are nice with large memory
> busses and very scalable SMP architectures.
>
Considering that Con's general mass target for his -ck patchset is
single-cored x86/PC-compatable system such as a Celeron or a
single-core Athlon with 32-256 MB RAM, (disclaimer: this is an
assumption) I think he is being rather sarcastic. The only other way
to interpret this is that those machines are totally different from
what Con uses for development, and as such, maybe Con'd find them
"lousy" because if something DID go wrong, it would be less obvious
he'd figure it out right away. But I think it's a joke, guys. >.>
--
~Mike
- Just the crazy copy cat.
next prev parent reply other threads:[~2007-03-13 13:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 23:58 Con Kolivas
2007-03-12 23:46 ` David Miller
2007-03-13 3:05 ` Con Kolivas
2007-03-13 4:32 ` Willy Tarreau
2007-03-13 5:03 ` [ck] " Felipe Alfaro Solana
2007-03-13 5:29 ` David Miller
2007-03-13 13:10 ` michael chang [this message]
2007-03-13 15:35 ` [ck] " Ash Milsted
2007-03-13 15:46 ` Con Kolivas
2007-03-13 15:53 ` Lee Revell
2007-03-13 17:45 ` Chris Friesen
2007-03-13 20:02 ` Lee Revell
2007-03-14 9:47 ` Ash Milsted
2007-03-15 2:31 ` Siddha, Suresh B
2007-03-15 6:05 ` Con Kolivas
2007-03-15 17:46 ` Siddha, Suresh B
2007-03-15 18:58 ` Ray Lee
2007-03-15 21:11 ` Con Kolivas
2007-03-15 21:12 ` Siddha, Suresh B
2007-03-17 14:27 ` Szonyi Calin
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=b14e81f00703130610r409290cex39e9bfa340f7dcbd@mail.gmail.com \
--to=thenewme91@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=davem@davemloft.net \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®