From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@digeo.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] deadline io scheduler
Date: Mon, 30 Sep 2002 10:15:22 +0200 [thread overview]
Message-ID: <20020930081522.GG27420@suse.de> (raw)
In-Reply-To: <20020926085445.A22321@eng2.beaverton.ibm.com>
On Thu, Sep 26 2002, Patrick Mansfield wrote:
> On Thu, Sep 26, 2002 at 08:59:51AM +0200, Jens Axboe wrote:
> > On Thu, Sep 26 2002, Jens Axboe wrote:
> > BTW, for SCSI, it would be nice to first convert more drivers to use the
> > block level queued tagging. That would provide us with a much better
> > means to control starvation properly on SCSI as well.
> >
> > --
> > Jens Axboe
>
> I haven't look closely at the block tagging, but for the FCP protocol,
> there are no tags, just the type of queueing to use (task attributes)
> - like ordered, head of queue, untagged, and some others. The tagging
> is normally done on the adapter itself (FCP2 protocol AFAIK). Does this
> mean block level queued tagging can't help FCP?
The generic block level tagging is nothing more than tag management. It
can 'tag' a request (assigning it an integer tag), and later let you
locate that request by giving it the tag.
I suspect you need none of that for FCP. Instead it looks more like you
can set the task attributes based on the type of request itself. So you
would currently set 'ordered' for a request with REQ_BARRIER set. And
you could set 'head of queue' for REQ_URGENT (I'm making this one up
:-), etc.
Do you need any request management to deal with FCP queueing? It doesn't
sound like it.
--
Jens Axboe
next prev parent reply other threads:[~2002-09-30 8:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 17:20 [PATCH] deadline io scheduler Jens Axboe
2002-09-26 6:15 ` Andrew Morton
2002-09-26 6:27 ` David S. Miller
2002-09-26 6:44 ` Jens Axboe
2002-09-26 6:59 ` Jens Axboe
2002-09-26 7:06 ` William Lee Irwin III
2002-09-26 7:06 ` David S. Miller
2002-09-26 7:16 ` Jeff Garzik
2002-09-26 7:13 ` David S. Miller
2002-09-26 7:33 ` Jeff Garzik
2002-09-26 7:35 ` David S. Miller
2002-09-26 8:15 ` Michael Clark
2002-09-26 8:18 ` William Lee Irwin III
2002-09-26 17:41 ` Mike Anderson
2002-09-26 18:03 ` Jeff Garzik
2002-09-26 19:21 ` Mike Anderson
2002-09-27 5:41 ` Andrew Vasquez
2002-09-27 5:57 ` Jeff Garzik
2002-09-27 16:58 ` Mike Anderson
2002-09-26 22:41 ` Matt Porter
2002-09-26 22:35 ` Mark Bellon
2002-09-26 20:21 ` Thomas Tonino
2002-09-26 7:41 ` Jeff Garzik
2002-09-26 7:23 ` William Lee Irwin III
2002-09-26 7:11 ` Jeff Garzik
2002-09-26 7:14 ` William Lee Irwin III
2002-09-26 15:54 ` Patrick Mansfield
2002-09-30 8:15 ` Jens Axboe [this message]
2002-09-30 15:39 ` Patrick Mansfield
2002-09-30 16:08 ` Jens Axboe
2002-09-26 8:28 ` Daniel Pittman
2002-09-26 8:29 ` Jens Axboe
2002-09-26 23:23 ` Daniel Pittman
2002-09-30 8:10 ` Jens Axboe
2002-09-26 15:09 ` Rik van Riel
2002-09-26 7:12 ` Andrew Morton
2002-09-26 7:17 ` Jens Axboe
2002-09-26 7:34 ` Jens Axboe
2002-09-30 7:45 ` Pavel Machek
2002-10-02 5:35 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2002-09-27 16:01 Andrew Vasquez
2002-09-27 17:07 ` Mike Anderson
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=20020930081522.GG27420@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--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