public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Storage Architect Part 1: Re: [PATCH] speed up SATA (resend 3)
Date: Tue, 30 Mar 2004 10:35:45 -0500	[thread overview]
Message-ID: <406993D1.8040705@techsource.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10403300000270.11654-100000@master.linux-ide.org>

Somehow I missed this discussion on the list, but I caught it on kerneltrap.

Anyhow, what I don't understand is why it would be so hard to have the 
block layer measure latency and dynamically adjust for each device. 
Start somewhat small, and when the block layer sees that a given device 
can handle larger requests without blowing latency requirements, 
increase the request size.  Keep a running average.


  reply	other threads:[~2004-03-30 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30  8:01 Storage Architect Part 1: Re: [PATCH] speed up SATA (resend 3) Andre Hedrick
2004-03-30 15:35 ` Timothy Miller [this message]
2004-03-31  8:09   ` Andre Hedrick

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=406993D1.8040705@techsource.com \
    --to=miller@techsource.com \
    --cc=andre@linux-ide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox