From: Matthew Wilcox <matthew@wil.cx>
To: Hifumi Hisashi <hifumi.hisashi@lab.ntt.co.jp>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sym2: Use ORDERED_QUEUE_TAG when barrier request is issued
Date: Mon, 13 Feb 2006 13:29:45 -0700 [thread overview]
Message-ID: <20060213202945.GL12822@parisc-linux.org> (raw)
In-Reply-To: <6.0.0.20.2.20060214004351.0424e5a0@129.60.53.12>
On Tue, Feb 14, 2006 at 01:10:54AM +0900, Hifumi Hisashi wrote:
> I think using ORDERED_QUEUE_TAG is preferable instead of
> SIMPLE_QUEUE_TAG when a request with barrier flag is
> issued.
This isn't enough; we don't know if the target device supports ordered
tags or not. The right way to do this is to convert sym2 to use the
midlayer tag code. I think it's nearly at a point where the conversion
is feasible. I'm going to push out the current set of cleanups next
week and then look at the problem again.
prev parent reply other threads:[~2006-02-13 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 16:10 [PATCH] sym2: Use ORDERED_QUEUE_TAG when barrier request is issued Hifumi Hisashi
2006-02-13 20:29 ` Matthew Wilcox [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=20060213202945.GL12822@parisc-linux.org \
--to=matthew@wil.cx \
--cc=hifumi.hisashi@lab.ntt.co.jp \
--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;
as well as URLs for NNTP newsgroup(s).