mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.x write barriers (updated for ext3)
Date: Mon, 25 Feb 2002 09:04:16 -0600	[thread overview]
Message-ID: <200202251504.g1PF4Gq01637@localhost.localdomain> (raw)
In-Reply-To: Message from Helge Hafting <helgehaf@aitel.hist.no>  of "Mon, 25 Feb 2002 11:57:35 +0100." <3C7A189F.8871B328@aitel.hist.no>

helgehaf@aitel.hist.no said:
> I just wonder - isn't the amount of outstanding requests a device can
> handle constant?  If so, the user could determine this (from spec or
> by running an utility that generates "too much" traffic.)   

The spec doesn't make any statements about this, so the devices are allowed to 
do whatever seems best.  Although it is undoubtedly implemented as a fixed 
queue on a few devices, there are others whose queue depth depends on the 
available resources (most disk arrays function this way---they tend to juggle 
tag queue depth dynamically per lun).

Even if the queue depth is fixed, you have to probe it dynamically because it 
will be different for each device.  Even worse, on a SAN or other shared bus, 
you might not be the only initiator using the device queue, so even for a 
device with a fixed queue depth you don't own all the slots so the queue depth 
you see varies.

The bottom line is that you have to treat the queue full return as a normal 
part of I/O flow control to SCSI devices.

James



  reply	other threads:[~2002-02-25 15:04 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 15:57 James Bottomley
2002-02-22 16:10 ` Chris Mason
2002-02-22 16:13 ` Stephen C. Tweedie
2002-02-22 17:36   ` James Bottomley
2002-02-22 18:14     ` Chris Mason
2002-02-28 15:36       ` James Bottomley
2002-02-28 15:55         ` Chris Mason
2002-02-28 17:58           ` Mike Anderson
2002-02-28 18:12         ` Chris Mason
2002-03-01  2:08           ` James Bottomley
2002-03-03 22:11         ` Daniel Phillips
2002-03-04  4:21           ` Jeremy Higdon
2002-03-04  5:31             ` Daniel Phillips
2002-03-04  6:09               ` Jeremy Higdon
2002-03-04  7:57                 ` Daniel Phillips
2002-03-05  7:09                   ` Jeremy Higdon
2002-03-05 22:56                     ` Daniel Phillips
2002-03-04 16:52                 ` Stephen C. Tweedie
2002-03-04 18:15                   ` Daniel Phillips
2002-03-05  7:40                     ` Jens Axboe
2002-03-05 22:29                       ` Daniel Phillips
2002-03-12  7:01                         ` Jens Axboe
2002-03-10  5:24                   ` Douglas Gilbert
2002-03-11 11:13                     ` Kurt Garloff
2002-03-12  6:58                       ` Jens Axboe
2002-03-13 22:37                         ` Peter Osterlund
2002-03-11 11:34                     ` Stephen C. Tweedie
2002-03-11 17:15                       ` James Bottomley
2002-03-12  1:17                     ` GOTO Masanori
2002-03-04 14:48           ` James Bottomley
2002-03-06 13:59             ` Daniel Phillips
2002-03-06 14:34               ` James Bottomley
2002-03-04  3:34         ` Chris Mason
2002-03-04  5:05           ` Daniel Phillips
2002-03-04 15:03             ` James Bottomley
2002-03-04 17:04               ` Stephen C. Tweedie
2002-03-04 17:35                 ` James Bottomley
2002-03-04 17:48                   ` Chris Mason
2002-03-04 18:11                     ` James Bottomley
2002-03-04 18:41                       ` Chris Mason
2002-03-04 21:34                       ` Stephen C. Tweedie
2002-03-04 18:09                   ` Stephen C. Tweedie
2002-03-04 17:16               ` Chris Mason
2002-03-04 18:05                 ` Stephen C. Tweedie
2002-03-04 18:28                   ` James Bottomley
2002-03-04 19:55                     ` Stephen C. Tweedie
2002-03-04 19:48                   ` Daniel Phillips
2002-03-04 19:57                     ` Stephen C. Tweedie
2002-03-04 21:06                       ` Daniel Phillips
2002-03-05 14:58                         ` Stephen C. Tweedie
2002-03-05  7:48                     ` Jens Axboe
2002-03-04 19:51                 ` Daniel Phillips
2002-03-05  7:42                   ` Jens Axboe
2002-03-04  8:19           ` Helge Hafting
2002-03-04 14:57           ` James Bottomley
2002-03-04 17:24             ` Chris Mason
2002-03-04 19:02               ` Daniel Phillips
2002-03-05  7:22             ` Jeremy Higdon
2002-03-05 23:01               ` Daniel Phillips
2002-02-25 10:57 ` Helge Hafting
2002-02-25 15:04   ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-01 15:26 Dieter Nützel
2002-03-01 16:00 ` James Bottomley
2002-02-21 23:30 Chris Mason
2002-02-22 14:19 ` Stephen C. Tweedie
2002-02-22 15:26 ` Chris Mason
2002-01-10  9:55 [ANNOUNCE] FUSE: Filesystem in Userspace 0.95 Miklos Szeredi
2002-01-13  3:10 ` Pavel Machek
2002-01-21 10:18 ` Miklos Szeredi
2002-01-23 10:47   ` Pavel Machek
2002-01-22 19:07 ` Daniel Phillips
2002-01-23  2:33   ` [Avfs] " Justin Mason
2002-01-23  5:26     ` Daniel Phillips

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=200202251504.g1PF4Gq01637@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=helgehaf@aitel.hist.no \
    --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®