All of lore.kernel.org
 help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: bharrosh@panasas.com
Cc: andi@firstfloor.org, James.Bottomley@hansenpartnership.com,
	linux-scsi@vger.kernel.org, bhalevy@panasas.com
Subject: Re: [RFC] Remove of ISA pools, and Lazy sense allocation.
Date: Thu, 8 May 2008 00:43:30 +0900	[thread overview]
Message-ID: <20080508004308U.tomof@acm.org> (raw)
In-Reply-To: <48218B24.4000507@panasas.com>

On Wed, 07 May 2008 13:57:40 +0300
Boaz Harrosh <bharrosh@panasas.com> wrote:

> Let me please explain a bit on my sense_buffer patchset and where I was going 
> with these:
> 
> Currently every ULD/Initiator that pushes request to block devices puts a sense
> buffer of SCSI_SENSE_BUFFERSIZE size onto request->sense pointer. scsi-midlayer
> shadows that buffer, for what it thought as a DMAable buffer for drivers, and at
> completion of request copies the shadow buffer back into ULD's buffer.
> 
> I have observed three uses of sense_buffer handling in scsi drivers:

I just had a quick look at only some of patches, but where do you
allocate rq->sense for fs requests?


Here are some comments:

scsi_eh: Define API for driver private sense allocation

+struct scsi_sense_elem {
+       union {
+               struct scsi_sense_elem *next;
+               u8 sense_data[SCSI_SENSE_BUFFERSIZE] ____cacheline_aligned;
+       };
+} ____cacheline_aligned;


I think that this is wrong since all the architecutures don't have
such dma restriction. ARCH_KMALLOC_MINALIGN?

There is the same code in The libata patch at least. I guess there are
more.

  reply	other threads:[~2008-05-07 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 10:57 [RFC] Remove of ISA pools, and Lazy sense allocation Boaz Harrosh
2008-05-07 15:43 ` FUJITA Tomonori [this message]
2008-05-12 13:03   ` Boaz Harrosh

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=20080508004308U.tomof@acm.org \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=andi@firstfloor.org \
    --cc=bhalevy@panasas.com \
    --cc=bharrosh@panasas.com \
    --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 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.