public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andreas Herrmann <AHERRMAN@de.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: [Patch] dont block device on QUEUE_FULL for last command
Date: Tue, 5 Aug 2003 08:07:45 +0200	[thread overview]
Message-ID: <20030805060745.GU854@suse.de> (raw)
In-Reply-To: <20030804154844.GB26775@gtf.org>

On Mon, Aug 04 2003, Jeff Garzik wrote:
> For most cases you _should_ block until another command is completed, at
> the very least.  Retrying the command immediately is _exactly_ the
> situation one wishes to avoid, when returning a QUEUE_FULL result!

Depends very much on who you ask :-)

-- 
Jens Axboe


  reply	other threads:[~2003-08-05  6:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 15:42 [Patch] dont block device on QUEUE_FULL for last command Andreas Herrmann
2003-08-04 15:48 ` Jeff Garzik
2003-08-05  6:07   ` Jens Axboe [this message]
2003-08-11  8:45     ` Kurt Garloff
2003-08-04 16:05 ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2003-08-05  7:15 Andreas Herrmann
2003-08-05  7:26 Andreas Herrmann
2003-08-05 13:08 ` Jeff Garzik

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=20030805060745.GU854@suse.de \
    --to=axboe@suse.de \
    --cc=AHERRMAN@de.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-scsi@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