All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18-pre9-ac1
Date: Tue, 12 Feb 2002 17:55:18 +0100	[thread overview]
Message-ID: <20020212175518.N1907@suse.de> (raw)
In-Reply-To: <20020212092658.Z729@suse.de> <E16ae1e-0001ws-00@the-village.bc.nu>
In-Reply-To: <E16ae1e-0001ws-00@the-village.bc.nu>

On Tue, Feb 12 2002, Alan Cox wrote:
> > > > 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.

That completely ignores that there is a _bug_ there currently. There was
a reason I removed disabled clustering, you know... 2.4 before the
change oopses, 2.4.18-preX (forget when Marcelo took the patch) has it
fixed.

> > 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.

You are probably right. Can't make pigs fly :-)

-- 
Jens Axboe


  reply	other threads:[~2002-02-12 16:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 23:01 Linux 2.4.18-pre9-ac1 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
2002-02-12 16:55           ` Jens Axboe [this message]
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=20020212175518.N1907@suse.de \
    --to=axboe@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andersen@codepoet.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.