From: Matthew Wilcox <matthew@wil.cx>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: James.Bottomley@HansenPartnership.com, bharrosh@panasas.com,
linux-scsi@vger.kernel.org, tomof@acm.org
Subject: Re: [PATCH v3] use dynamically allocated sense buffer
Date: Sun, 20 Jan 2008 21:37:41 -0700 [thread overview]
Message-ID: <20080121043741.GF27250@parisc-linux.org> (raw)
In-Reply-To: <20080121130858G.fujita.tomonori@lab.ntt.co.jp>
On Mon, Jan 21, 2008 at 01:08:58PM +0900, FUJITA Tomonori wrote:
> On Sun, 20 Jan 2008 09:40:11 -0700
> Matthew Wilcox <matthew@wil.cx> wrote:
> > Longer-term, I want to allow low-level drivers to allocate the
> > sense_buffer themselves so they can DMA directly into it (ie grown-up dma
> > mapping, rather than this quaint x86 __GFP_DMA). This patch doesn't get
>
> Yeah, I think that the approach is one of candidates.
>
> If we go with it, I think that the major issue is that LLDs don't know
> when they can reclaim sense_buffer from scsi-ml; scsi-ml uses
> sense_buffer after scmd->scsi_done.
The midlayer would call a function in the scsi_host_template to free the
command. The sense_buffer would be freed at the same time.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-01-21 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 4:32 [PATCH v3] use dynamically allocated sense buffer FUJITA Tomonori
2008-01-20 16:04 ` Boaz Harrosh
2008-01-20 16:36 ` James Bottomley
2008-01-21 3:59 ` FUJITA Tomonori
2008-01-23 18:26 ` Boaz Harrosh
2008-01-20 16:40 ` Matthew Wilcox
2008-01-21 4:08 ` FUJITA Tomonori
2008-01-21 4:37 ` Matthew Wilcox [this message]
2008-01-22 4:21 ` FUJITA Tomonori
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=20080121043741.GF27250@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=tomof@acm.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).