From: Nick Piggin <nickpiggin@yahoo.com.au>
To: FabF <Fabian.Frederick@skynet.be>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: IDE throughput in 2.6 - it's good!
Date: Sun, 25 Apr 2004 09:58:20 +1000 [thread overview]
Message-ID: <408AFF1C.903@yahoo.com.au> (raw)
In-Reply-To: <1082820563.2268.10.camel@bluerhyme.real3>
FabF wrote:
> Here's what we can call a server direction.2.6 is unbeatable there due
> to IO scheduler (i.e. As-iosched, cfq and noop rock'n'roll)
Well, which one were you using just now? AS I assume?
>
> There are no good conclusions at all although ,at this state of
> development, IMHO, 2.4 seems more 'client friendly' and 2.6 server
> oriented in this chapter.
IO scheduler wise, AS should be good for "clients" (ie. desktop)
because it is the desktop where AS's possible small throughput
regressions are not a big problem even if they did arise.
next prev parent reply other threads:[~2004-04-24 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 15:29 RE:IDE throughput in 2.6 - it's good! FabF
2004-04-24 23:58 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-23 21:56 IDE " Ken Moffat
2004-04-27 15:38 ` Timothy Miller
2004-04-27 19:17 ` Ken Moffat
2004-04-27 20:43 ` Timothy Miller
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=408AFF1C.903@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Fabian.Frederick@skynet.be \
--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