From: Daniel Phillips <phillips@bonn-fries.net>
To: James Bottomley <James.Bottomley@steeleye.com>,
Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] queue barrier support
Date: Sat, 16 Feb 2002 11:20:33 +0100 [thread overview]
Message-ID: <E16c1xJ-0002qR-00@starship.berlin> (raw)
In-Reply-To: <200202131826.g1DIQCT02506@localhost.localdomain>
In-Reply-To: <200202131826.g1DIQCT02506@localhost.localdomain>
On February 13, 2002 07:26 pm, James Bottomley wrote:
> A problem (that is probably only an issue for older drives) is that while
> technically the standard requires all 3 types of TAG to be supported if tag
> queueing is, some drives really only have simple tag support in their
> firmware, so you may need to add a blacklist for ordered tags on certain
> drives.
>From user space, I hope.
--
Daniel
next prev parent reply other threads:[~2002-02-16 10:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 18:26 James Bottomley
2002-02-15 9:02 ` Jens Axboe
2002-02-15 15:15 ` James Bottomley
2002-02-15 16:28 ` Chris Mason
2002-02-15 16:51 ` James Bottomley
2002-02-15 17:17 ` Chris Mason
2002-02-15 17:48 ` James Bottomley
2002-02-15 22:30 ` Matthias Andree
2002-02-15 17:09 ` James Bottomley
2002-02-15 16:43 ` Mike Anderson
2002-02-15 13:41 ` Chris Mason
2002-02-16 10:20 ` Daniel Phillips [this message]
2002-02-16 15:02 ` James Bottomley
2002-02-25 20:55 ` 929-Emulex, ABTS Command Anamoly! Cindy Sweet
2002-02-25 21:02 ` arjan
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 12:51 [PATCH] queue barrier support Jens Axboe
2002-02-13 13:09 ` Martin Dalecki
2002-02-13 13:13 ` Jens Axboe
2002-02-13 14:36 ` Martin Dalecki
2002-02-13 14:41 ` Jens Axboe
2002-02-13 14:51 ` Daniel Phillips
2002-02-13 15:18 ` Jens Axboe
2002-02-13 17:47 ` Andreas Dilger
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=E16c1xJ-0002qR-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=James.Bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®