From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Ed Lin <ed.lin@promise.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
hch <hch@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
promise_linux <promise_linux@promise.com>
Subject: Re: [PATCH] Promise 'stex' driver
Date: Fri, 21 Jul 2006 03:07:24 +0200 [thread overview]
Message-ID: <20060721010724.GB24176@suse.de> (raw)
In-Reply-To: <44C01CD7.4030308@garzik.org>
On Thu, Jul 20 2006, Jeff Garzik wrote:
> James Bottomley wrote:
> >On Thu, 2006-07-20 at 17:27 -0400, Jeff Garzik wrote:
> >>Since _no individual SCSI driver_ uses the block layer
> >>tagging, it is likely that some instability and core kernel
> >>development
> >>will occur, in order to make that work.
> >
> >That's not quite true: 53c700 and tmscsim both use it ... I could with
> >the usage were wider, but at least 53c700 has pretty regular and
> >constant usage ... enough I think to validate the block tag code (it's
> >been using it for the last three years).
>
> Not for the case being discussed in this thread, adapter-wide tags.
That just means the map is shared, otherwise there should be little if
any difference.
> AFAICS, no file in include/scsi/* or drivers/scsi/* ever calls
> blk_queue_init_tags() with a non-NULL third arg.
grpe again, it's in scsi_tcq.h.
> The block tagging capability being discussed here is poorly validated
> due to overall underuse, and its never been used in SCSI AFAIK.
It has and is, James uses it every day!
--
Jens Axboe
next prev parent reply other threads:[~2006-07-21 1:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 15:07 [PATCH] Promise 'stex' driver Ed Lin
2006-07-20 21:27 ` Jeff Garzik
2006-07-20 23:55 ` James Bottomley
2006-07-21 0:16 ` Jeff Garzik
2006-07-21 1:07 ` Jens Axboe [this message]
2006-07-21 1:25 ` Jeff Garzik
2006-07-21 1:38 ` Jens Axboe
2006-07-21 2:10 ` Jeff Garzik
2006-07-21 2:36 ` Jens Axboe
2006-07-21 3:01 ` Jeff Garzik
2006-07-21 3:18 ` Jens Axboe
2006-07-21 3:52 ` Jeff Garzik
2006-07-21 12:13 ` Jens Axboe
2006-07-23 19:45 ` hch
2006-07-23 20:21 ` Jeff Garzik
2006-07-23 19:44 ` hch
2006-07-21 1:06 ` Jens Axboe
[not found] <NONAMEBFJ3sl3xbYiMC000000d4@nonameb.ptu.promise.com>
2006-07-25 9:26 ` hch
2006-07-26 1:20 ` Alan Cox
2006-07-25 17:30 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-06-10 16:08 Jeff Garzik
2006-06-10 16:10 ` Christoph Hellwig
2006-06-10 16:29 ` James Bottomley
2006-06-10 16:34 ` Christoph Hellwig
2006-06-10 16:50 ` Jeff Garzik
2006-06-10 17:10 ` Christoph Hellwig
2006-06-10 16:30 ` Jeff Garzik
2006-06-10 17:06 ` Christoph Hellwig
2006-06-10 17:37 ` Jeff Garzik
2006-06-10 18:22 ` James Bottomley
2006-06-10 18:43 ` Jeff Garzik
2006-06-10 22:28 ` Jeff Garzik
2006-06-10 17:47 ` Alexey Dobriyan
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=20060721010724.GB24176@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=ed.lin@promise.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=promise_linux@promise.com \
/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.