From: "Dan Maas" <dmaas@dcine.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: IO degradation in 2.4.17-pre2 vs. 2.4.16
Date: Tue, 11 Dec 2001 17:37:55 -0500 [thread overview]
Message-ID: <048e01c18294$7a497650$1a01a8c0@allyourbase> (raw)
In-Reply-To: <fa.n0jjs6v.7ms98a@ifi.uio.no> <fa.jlqjvuv.348ign@ifi.uio.no>
> > Yes, throughtput-only tests will have their numbers degradated with the
> > change applied on 2.4.16-pre2.
> >
> > The whole thing is just about tradeoffs: Interactivity vs throughtput.
> >
> > I'm not going to destroy interactivity for end users to get beatiful
> > dbench numbers.
>
> Latency is more of an issue for end user machines.
Time for CONFIG_OPTIMIZE_THROUGHPUT / CONFIG_OPTIMIZE_LATENCY ?
Dan
next parent reply other threads:[~2001-12-11 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.n0jjs6v.7ms98a@ifi.uio.no>
[not found] ` <fa.jlqjvuv.348ign@ifi.uio.no>
2001-12-11 22:37 ` Dan Maas [this message]
2001-12-11 21:44 ` IO degradation in 2.4.17-pre2 vs. 2.4.16 Marcelo Tosatti
2001-12-11 23:14 ` Alan Cox
2001-12-12 0:23 ` Andrew Morton
2001-12-12 0:52 ` J Sloan
2001-12-01 19:16 Jason Holmes
2001-12-01 21:34 ` Andrew Morton
2001-12-01 22:35 ` Jason Holmes
2001-12-03 19:22 ` Marcelo Tosatti
2001-12-03 23:32 ` Jason Holmes
2001-12-11 22:37 ` Bill Davidsen
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='048e01c18294$7a497650$1a01a8c0@allyourbase' \
--to=dmaas@dcine.com \
--cc=davidsen@tmr.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