From: Mike Christie <michaelc@cs.wisc.edu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: dougg@torque.net, tomof@acm.org, linux-scsi@vger.kernel.org,
James.Bottomley@SteelEye.com, jens.axboe@oracle.com
Subject: Re: [PATCH] sg: increase sglist_len of the sg_scatter_hold structure
Date: Wed, 08 Aug 2007 12:20:43 -0500 [thread overview]
Message-ID: <46B9FB6B.70501@cs.wisc.edu> (raw)
In-Reply-To: <46B9F626.9020200@cs.wisc.edu>
Mike Christie wrote:
> For drivers like sg and st, do mean the the sg list that is passed to
> functions like scsi_execute_async? If we kill that argument, and instead
> have sg.c and other scsi_execute_async callers just call blk helpers
> like blk_rq_map_user then we would not have to worry about drivers like
> sg needing to know about chaining right? I mean sg.c would not every
> interact with a scatterlist. It would just interact with a request and
> the blk helpers map data for it.
There should be a return there.
The scatterlist that sg and st interact
> with is bogus. It gets thrown away in scsi_execute_async and is only
> used for book keeping.
I mean currently the scatterlist that sg and st use is bogus and gets
thrown away. If we convert sg and st to use blk_rq_map_user then those
drivers will not have to interact with a scatterlist at all.
next prev parent reply other threads:[~2007-08-08 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 15:31 [PATCH] sg: increase sglist_len of the sg_scatter_hold structure FUJITA Tomonori
2007-08-05 16:55 ` Douglas Gilbert
2007-08-06 4:09 ` FUJITA Tomonori
2007-08-07 17:13 ` Mike Christie
2007-08-07 22:38 ` FUJITA Tomonori
2007-08-08 7:15 ` Jens Axboe
2007-08-08 16:58 ` Mike Christie
2007-08-08 17:20 ` Mike Christie [this message]
2007-08-09 7:33 ` Benny Halevy
2007-08-09 13:43 ` FUJITA Tomonori
2007-08-09 13:43 ` 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=46B9FB6B.70501@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=dougg@torque.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--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.