From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: axboe@suse.de (Jens Axboe)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18-pre9-ac1
Date: Tue, 12 Feb 2002 14:35:18 +0000 (GMT) [thread overview]
Message-ID: <E16ae1e-0001ws-00@the-village.bc.nu> (raw)
In-Reply-To: <20020212092658.Z729@suse.de> from "Jens Axboe" at Feb 12, 2002 09:26:58 AM
> > > I want to find out why it was done first and then test it. Leaving it out
> > > will ensure it bugs me until I test it
> >
> > If you leave it out, you surely want to make sure that the other request
> > init and re-init paths agree on the clustering for MO devices. Because
> > they don't.
No - I want to run a test set with an M/O drive before and after the change
and see what it shows in real life. I suspect nothing much.
> Now, disabling request merging for MO devices might make a whole lot
> more sense. That might be worth while trying, and I'd be happy to give
> you a patch to try that out instead.
I don't think that should be required actually. The killer on M/O disks
is seek time, and to an extent rotational latency (its 3 trips round a
cheaper M/O disk to rewrite a sector). If anything clustering writes to
the same track should be a big win.
Alan
next prev parent reply other threads:[~2002-02-12 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 23:01 Alan Cox
2002-02-12 0:15 ` Erik Andersen
2002-02-12 0:34 ` Alan Cox
2002-02-12 8:21 ` Jens Axboe
2002-02-12 8:26 ` Jens Axboe
2002-02-12 14:35 ` Alan Cox [this message]
2002-02-12 16:55 ` Jens Axboe
2002-02-12 18:40 ` Bill Davidsen
2002-02-12 20:05 ` Erik Andersen
2002-02-12 0:53 ` Pozsar Balazs
2002-02-12 1:00 ` Alan Cox
2002-02-12 4:46 ` Nick Orlov
2002-02-12 13:30 ` Pozsar Balazs
2002-02-12 15:13 ` Thomas Capricelli
2002-02-12 15:39 ` Alan Cox
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=E16ae1e-0001ws-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andersen@codepoet.org \
--cc=axboe@suse.de \
--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
all inboxes | Powered by JetHome®