From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <tomof@acm.org>
Cc: linux-scsi@vger.kernel.org, dougg@torque.net
Subject: Re: [PATCH 4/6] bsg: add sg_io_v4 structure
Date: Fri, 22 Dec 2006 09:42:24 +0100 [thread overview]
Message-ID: <20061222084224.GM17199@kernel.dk> (raw)
In-Reply-To: <20061222134635M.fujita.tomonori@lab.ntt.co.jp>
On Fri, Dec 22 2006, FUJITA Tomonori wrote:
> From: Jens Axboe <jens.axboe@oracle.com>
> Subject: Re: [PATCH 4/6] bsg: add sg_io_v4 structure
> Date: Thu, 21 Dec 2006 08:28:23 +0100
>
> > On Thu, Dec 21 2006, FUJITA Tomonori wrote:
> > > From: Jens Axboe <jens.axboe@oracle.com>
> > > Subject: Re: [PATCH 4/6] bsg: add sg_io_v4 structure
> > > Date: Wed, 20 Dec 2006 11:13:14 +0100
> > >
> > > > On Wed, Dec 20 2006, FUJITA Tomonori wrote:
> > > > > This patch adds sg_io_v4 structure that Doug proposed last month.
> > > > >
> > > > > There's one major change from the RFC. I dropped iovec, which needs
> > > > > compat stuff. The bsg code simply calls blk_rq_map_user against
> > > > > dout_xferp/din_xferp. So if possible, the page frames are directly
> > > > > mapped. If not possible, the block layer allocates new page frames and
> > > > > does memory copies.
> > > > >
> > > > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > > > > ---
> > > > > include/linux/bsg.h | 43 +++++++++++++++++++++++++++++++++++++++++++
> > > > > 1 files changed, 43 insertions(+), 0 deletions(-)
> > > > >
> > > > > diff --git a/include/linux/bsg.h b/include/linux/bsg.h
> > > > > index dc0d728..0d212cc 100644
> > > > > --- a/include/linux/bsg.h
> > > > > +++ b/include/linux/bsg.h
> > > > > @@ -1,6 +1,47 @@
> > > > > #ifndef BSG_H
> > > > > #define BSG_H
> > > > >
> > > > > +struct sg_io_v4 {
> > > > > + int32_t guard; /* [i] 'Q' to differentiate from v3 */
> > > > > + uint32_t protocol; /* [i] 0 -> SCSI , .... */
> > > >
> > > > I prefer using the u32 types and so on for explicitly sized variables.
> > > > I'll make that change.
> > >
> > > I see though we need to use __u32 instead of u32, don't we?
> >
> > Yep, we should.
>
> Are you waiting for a patch?
Not really, just didn't get to it yet. But I'll take the patch, thanks
:-)
Could you do the __user annotations as well?
--
Jens Axboe
prev parent reply other threads:[~2006-12-22 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 5:43 [PATCH 4/6] bsg: add sg_io_v4 structure FUJITA Tomonori
2006-12-20 10:13 ` Jens Axboe
2006-12-20 22:29 ` FUJITA Tomonori
2006-12-21 7:28 ` Jens Axboe
2006-12-22 4:46 ` FUJITA Tomonori
2006-12-22 8:42 ` Jens Axboe [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=20061222084224.GM17199@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dougg@torque.net \
--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 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.