From: Jeff Garzik <jeff@garzik.org>
To: Ed Lin <ed.lin@promise.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"promise_linux@promise.com" <promise_linux@promise.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.16-rc6] Promise SuperTrak driver
Date: Thu, 16 Mar 2006 00:11:08 -0500 [thread overview]
Message-ID: <4418F36C.1090508@garzik.org> (raw)
In-Reply-To: <NONAMEBSkcJse1fTvOS000001bc@nonameb.ptu.promise.com>
Ed Lin wrote:
> I think the tcq is good after reading the related kernel code. But driver
> still need to keep track of the tag for eh and flush. Maybe the driver
> can use find_first_zero_bit(), __set_bit(), and __test_and_clear_bit(),
> because this is what the block layer uses for tag operations.
Once mapped by the block layer, the tag should be accessible via struct
request::tag variable for the lifetime of the struct request.
Jeff
next parent reply other threads:[~2006-03-16 5:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NONAMEBSkcJse1fTvOS000001bc@nonameb.ptu.promise.com>
2006-03-16 5:11 ` Jeff Garzik [this message]
[not found] <NONAMEBK04QBh0TzlYb000006b5@nonameb.ptu.promise.com>
2006-03-31 15:21 ` [PATCH 2.6.16-rc6] Promise SuperTrak driver Jeff Garzik
2006-03-13 22:41 Jeff Garzik
2006-03-13 23:42 ` Andrew Morton
2006-03-14 10:50 ` Jan-Benedict Glaw
2006-03-14 20:04 ` Matthew Wilcox
2006-03-16 23:55 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 13:17 Ed Lin
2006-03-13 10:38 Ed Lin
2006-03-14 3:20 ` Andrew Morton
2006-03-14 7:13 ` Jeff Garzik
2006-03-14 9:18 ` Arjan van de Ven
2006-03-14 9:27 ` Jeff Garzik
2006-03-14 9:40 ` Arjan van de Ven
2006-03-14 15:12 ` Bob Copeland
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=4418F36C.1090508@garzik.org \
--to=jeff@garzik.org \
--cc=ed.lin@promise.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--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.