From: Giuliano Pochini <pochini@shiny.it>
To: Andrew Morton <akpm@zip.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: RE: [patch, CFT] improved disk read latency
Date: Mon, 07 Jan 2002 15:20:07 +0100 (CET) [thread overview]
Message-ID: <XFMail.20020107152007.pochini@shiny.it> (raw)
In-Reply-To: <3C396A66.D19E71DF@zip.com.au>
> + if (__rq->elevator_sequence-- <= 0) {
> + /*
> + * OK, we've exceeded someone's latency limit.
> + * But we still continue to look for merges,
> + * because they're so much better than seeks.
> + */
> + merge_only = 1;
That's true for hard discs, but for most removables seek time is
small compared to write time. Think about a magneto-optical drive or
a ZIP. Seek is about 20-50ms while writing goes at 300-1000KiB/s.
Bye.
prev parent reply other threads:[~2002-01-07 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 9:29 [patch, CFT] improved disk read latency Andrew Morton
2002-01-07 14:20 ` Giuliano Pochini [this message]
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=XFMail.20020107152007.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=akpm@zip.com.au \
--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