From: Muli Ben-Yehuda <muli@il.ibm.com>
To: FUJITA Tomonori <tomof@acm.org>
Cc: James.Bottomley@SteelEye.com, jens.axboe@oracle.com,
hch@infradead.org, jeff@garzik.org, gregkh@suse.de, hare@suse.de,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH 0/5] fix iommu sg list merge problem
Date: Wed, 26 Sep 2007 12:02:21 +0200 [thread overview]
Message-ID: <20070926100221.GW4239@rhun.haifa.ibm.com> (raw)
In-Reply-To: <20070925142141N.tomof@acm.org>
On Wed, Sep 26, 2007 at 05:57:57PM +0900, FUJITA Tomonori wrote:
> iommu code merges sg lists without considering lld's restrictions so
> some llds need a workaround to split sg lists again. This patchset
> fixes iommu to handle lld's max segment size limit properly.
The patches look reasonable to me.
> This patchset includes only the x86_64 iommu patch
There are multiple x86-64 IOMMUs, but only GART is in-tree and
supports merging.
> but my git tree includes x86_64, ppc, ia64, parisc, and alpha
> patches. As far as I know, thye are all the iommu code that merges
> sg lists. The iommu patchse are only compile tested.
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tomo/linux-2.6-bidi.git iommu
Do you think it will be possible to abstract the merging code into
common code, rather than duplicating it for every IOMMU?
Cheers,
Muli
next prev parent reply other threads:[~2007-09-26 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 8:57 [PATCH 0/5] fix iommu sg list merge problem FUJITA Tomonori
2007-09-26 10:02 ` Muli Ben-Yehuda [this message]
2007-09-26 14:34 ` FUJITA Tomonori
2007-09-26 14:38 ` James Bottomley
2007-09-26 14:48 ` 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=20070926100221.GW4239@rhun.haifa.ibm.com \
--to=muli@il.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gregkh@suse.de \
--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