All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Liran Schour <LIRANS@il.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SCSI commands order when using scsi_do_req
Date: Fri, 17 Jun 2005 13:08:41 +0400	[thread overview]
Message-ID: <42B29319.5050704@vlnb.net> (raw)
In-Reply-To: <1117734886.5025.55.camel@mulgrave>

James Bottomley wrote:
> On Thu, 2005-06-02 at 20:31 +0300, Liran Schour wrote:
> 
>>I am developing a new SCSI upper layer driver. (Object based SCSI device)
>>I noticed that scsi_do_req execute commands in LIFO order (add new commands
>>to the head of the Q).
>>This behavior can cause a starvation of commands (or at least long delays).
>>What is the proper solution to this?
> 
> 
> Well, to use the proper interfaces.
> 
> scsi_do_req is deprecated, so don't use it.  scsi_wait_req is its
> replacement.  Note: they're only really intended to allow ULDs to
> execute commands that are necessary for controlling the device (that's
> why they go at the head of the queue).  Block commands are executed in
> order using ULD init_command() (or REQ_BLOCK_PC).

Hm, st/osst/sg use scsi_do_req(), so should we consider those drivers 
broken in async mode? Apparently, a user in this mode could write not 
what he/she intented, the order could be wrong. Or do I miss something?

Vlad

      parent reply	other threads:[~2005-06-17  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 17:31 SCSI commands order when using scsi_do_req Liran Schour
2005-06-02 17:54 ` James Bottomley
2005-06-03  0:03   ` Douglas Gilbert
2005-06-06  8:32     ` Liran Schour
2005-06-06 14:32       ` James Bottomley
2005-06-07  9:27         ` Liran Schour
2005-06-17  9:08   ` Vladislav Bolkhovitin [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=42B29319.5050704@vlnb.net \
    --to=vst@vlnb.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=LIRANS@il.ibm.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 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.