public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Guillaume Lacôte" <Guillaume@Lacote.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BIO ordering and NativeCommandQueueing
Date: Tue, 15 Jun 2004 13:36:48 +0200	[thread overview]
Message-ID: <20040615113647.GJ25903@suse.de> (raw)
In-Reply-To: <200406151202.12884.Guillaume@Lacote.name>

On Tue, Jun 15 2004, Guillaume Lacôte wrote:
> Hello,
> (I hope this is the right place for this - sorry if it is not).
> 
> Native Command Queueing (and Tagged Command Queueing) is a feature
> provided by the hardware of newer IDE (and old SCSI) disk drives which
> basically consists in reordering the commands issued on the ATA bus to
> improve speed.
> 
> I assume however that the fastest way to read sectors 101 to 110 is to
> ask for them in that order: 101,102,...,110 . This is a basic
> assumption made by most OSes and apps I presume (otherwise for example
> DMA performance would be catastrophic).
> 
> Here is my point: since a bvec consists of _ordered_ requests only,
> what is the use of NCQ ? Requests will arrive to the drive in
> increasing order, which is the best possible ordering
> performance-wise; thus NCQ will do never do anything.

I think you are confusing scatter-gather with request ordering. And your
terminology is off base - a bvec doesn't consist of ordered requests, it
consist of (max) a single page. A bio consists of bvec's. A request
consits of ordered bio's. The drive queue consist of (fairly well)
ordered requests.

I won't go on about merrits of queueing and depths, search the archives
for that.

-- 
Jens Axboe


      reply	other threads:[~2004-06-15 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 10:02 BIO ordering and NativeCommandQueueing Guillaume Lacôte
2004-06-15 11:36 ` Jens Axboe [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=20040615113647.GJ25903@suse.de \
    --to=axboe@suse.de \
    --cc=Guillaume@Lacote.name \
    --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