public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Linton <jli@greshamstorage.com>
To: Dan Aloni <da-x@monatomic.org>
Cc: Arjan van de Ven <arjan@fenrus.demon.nl>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org, Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH] scsi_execute_async() should add to the tail of the queue
Date: Wed, 20 Dec 2006 17:50:51 -0600	[thread overview]
Message-ID: <4589CC5B.9090704@greshamstorage.com> (raw)
In-Reply-To: <4587C04E.10307@monatomic.org>

> So instead of adding a parameter, we can make scsi_execute_async()
> decide for itself based on the SCSI command, with read/write I/Os
> taking the lowest priority.
	This seems like a bad idea, I can come up with a number of cases where 
the priority of a request would better be optimized by a higher level 
subsystem, rather than a simple prioritization based on the command type.

The original suggestion to provide both head and tail insertion options 
seems like the obvious solution, short of a full priority queuing system.





  reply	other threads:[~2006-12-21  0:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19  8:35 [PATCH] scsi_execute_async() should add to the tail of the queue Dan Aloni
2006-12-19 10:03 ` Arjan van de Ven
2006-12-19 10:34   ` Dan Aloni
2006-12-20 23:50     ` Jeremy Linton [this message]
2006-12-19 11:26   ` Jens Axboe
2006-12-19 18:34     ` Jon Escombe
2006-12-19 18:44       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2006-12-19  0:02 Dan Aloni
2006-12-20 20:40 ` Steven Hayter
2006-12-21  7:12   ` Dan Aloni

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=4589CC5B.9090704@greshamstorage.com \
    --to=jli@greshamstorage.com \
    --cc=arjan@fenrus.demon.nl \
    --cc=da-x@monatomic.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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