public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomof@acm.org>
To: bharrosh@panasas.com
Cc: tomof@acm.org, linux-scsi@vger.kernel.org, jens.axboe@oracle.com,
	James.Bottomley@SteelEye.com, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH 0/9] scsi_data_buffer structure (in preparation for bidi)
Date: Sun, 9 Sep 2007 23:46:51 +0900	[thread overview]
Message-ID: <20070909055725N.tomof@acm.org> (raw)
In-Reply-To: <46E3FE8B.8020401@panasas.com>

On Sun, 09 Sep 2007 17:09:15 +0300
Boaz Harrosh <bharrosh@panasas.com> wrote:

> On Sun, Sep 09 2007 at 16:47 +0300, FUJITA Tomonori <tomof@acm.org> wrote:
> > On Sun, 09 Sep 2007 11:25:57 +0300
> > Boaz Harrosh <bharrosh@panasas.com> wrote:
> > 
> >> On Fri, Sep 07 2007 at 0:50 +0300, FUJITA Tomonori <tomof@acm.org> wrote:
> >>> This patchset, which I submitted before, adds a new data structure, 
> >>> scsi_data_buffer, including everything for data transfer:
> >>>
> >>> struct scsi_data_buffer { unsigned length; int resid; short sg_count;
> >>>  short __sg_count; struct scatterlist *sglist; };
> >>>
> >>> One scsi_data_buffer structure is embedded in struct scsi_cmnd for 
> >>> uni-directional transfer. All the members are just moved from 
> >>> scsi_cmnd structure to scsi_data_buffer structure. So nothing is
> >>> added to scsi_cmnd structure.
> >>>
> >>> After applying this patchset, llds must use the scsi data accessors.
> >>> This patchset includes some conversation patches (most of them are
> >>> patches that Boaz submitted before), however there is still some code
> >>> that is needed to be converted.
> >>>
> >>> Boaz, if you still have other conversation patches, please submit 
> >>> them.
> >>>
> >>> I suspect that nobody cares about some of unconverted llds, which
> >>> will be not compilable after this patchset. I'll fix ldds that people
> >>>  complain about.
> >>>
> >>> It's difficult to test this patchset in -mm via scsi-misc. Jens, 
> >>> please send this to -mm via the block tree.
> >> Sorry for the late response. Just am back from vacation.
> >>
> >> Tomo please hold with these patches a bit longer the
> >> Tree is not ready for it. 
> > 
> > Then we have no chance to merge scsi_data_buffer into 2.6.24.
> > 
> I hope to submit all/most of the work this week. If we miss the window
> for 2.6.24 than I'm very sorry for that. But I don't think we are 
> aloud to break USB storage subsystem.

I'll send patches for USB (in a 'search and replace' way) if you don't
soon. Except for USB, I suspect that nobody cares about most of the
unconverted drivers.

      reply	other threads:[~2007-09-09 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 21:50 [PATCH 0/9] scsi_data_buffer structure (in preparation for bidi) FUJITA Tomonori
2007-09-06 21:52 ` FUJITA Tomonori
2007-09-09  8:25 ` Boaz Harrosh
2007-09-09 13:47   ` FUJITA Tomonori
2007-09-09 14:09     ` Boaz Harrosh
2007-09-09 14:46       ` FUJITA Tomonori [this message]

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=20070909055725N.tomof@acm.org \
    --to=tomof@acm.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=bharrosh@panasas.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jens.axboe@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox