From: Greg KH <gregkh@suse.de>
To: FUJITA Tomonori <tomof@acm.org>
Cc: James.Bottomley@SteelEye.com, jens.axboe@oracle.com,
hch@infradead.org, jeff@garzik.org, hare@suse.de,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH 3/5] add sg segment limitation info to device structure
Date: Wed, 26 Sep 2007 09:05:58 -0700 [thread overview]
Message-ID: <20070926160558.GA10819@suse.de> (raw)
In-Reply-To: <20070925142157B.tomof@acm.org>
On Wed, Sep 26, 2007 at 05:58:01PM +0900, FUJITA Tomonori wrote:
> iommu code merges sg segments without considering lld's sg segment
> restrictions. iommu code can't access to the limitations because they
> are in request_queue. This patch adds max_segment_size to device
> structure. seg_boundary_mask will be added too later.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> ---
> include/linux/device.h | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/device.h b/include/linux/device.h
> index 3a38d1f..8046b60 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -443,6 +443,13 @@ struct device {
>
> struct dma_coherent_mem *dma_mem; /* internal for coherent mem
> override */
> +
> + /*
> + * a low level driver may set these to teach IOMMU code about
> + * sg limitations.
> + */
> + unsigned int max_segment_size;
Does this really need to be here? Can't it go into the bus specific
device that needs this?
thanks,
greg k-h
next prev parent reply other threads:[~2007-09-26 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 8:58 [PATCH 3/5] add sg segment limitation info to device structure FUJITA Tomonori
2007-09-26 16:05 ` Greg KH [this message]
2007-09-27 0:37 ` FUJITA Tomonori
2007-10-01 23:36 ` James Bottomley
2007-10-02 1:39 ` Matthew Wilcox
2007-10-02 4:22 ` Greg KH
2007-10-02 14:45 ` James Bottomley
2007-10-02 15:02 ` Kay Sievers
2007-10-02 15:05 ` James Bottomley
2007-10-02 15:10 ` Kay Sievers
2007-10-02 15:14 ` James Bottomley
2007-10-02 15:23 ` Kay Sievers
2007-10-02 15:25 ` Matthew Wilcox
2007-10-02 16:44 ` Greg KH
2007-10-03 14:19 ` FUJITA Tomonori
2007-10-03 17:57 ` Jeff Garzik
2007-10-03 21:50 ` Greg KH
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=20070926160558.GA10819@suse.de \
--to=gregkh@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--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 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).