From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Lord <liml@rtr.ca>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
James Bottomley <James.Bottomley@steeleye.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: libata+SGIO: is .dma_boundary respected?
Date: Tue, 21 Mar 2006 20:42:15 +0100 [thread overview]
Message-ID: <20060321194215.GP4285@suse.de> (raw)
In-Reply-To: <44205642.7070302@pobox.com>
On Tue, Mar 21 2006, Jeff Garzik wrote:
> Jens Axboe wrote:
> >My explanation was for the block layer part of course, I'm hoping (did
> >not check) that the iommu has similar sane defaults.
>
> Part of the problem is that the iommu doesn't know as much as the block
> layer.
Right, this is what needs fixing.
> >But this still really wants a unification of the dma restrictions...
>
> Strongly agreed. ISTR JamesB had some concrete thoughts in that
> direction, but they never made it beyond an IRC channel and/or a few
> emails.
The pci dev already holds the dma address, we could add dma boundary and
dma segment size as well?
--
Jens Axboe
next prev parent reply other threads:[~2006-03-21 19:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 20:48 libata+SGIO: is .dma_boundary respected? Mark Lord
2006-03-19 21:14 ` Jeff Garzik
2006-03-19 21:19 ` Mark Lord
2006-03-19 21:38 ` Jeff Garzik
2006-03-19 21:45 ` Mark Lord
2006-03-19 21:54 ` Mark Lord
2006-03-21 1:18 ` Jeff Garzik
2006-03-21 4:43 ` Mark Lord
2006-03-21 6:14 ` Jeff Garzik
2006-03-21 13:59 ` Mark Lord
2006-03-21 18:42 ` Jens Axboe
2006-03-21 19:18 ` Mark Lord
2006-03-21 19:29 ` Jeff Garzik
2006-03-21 19:31 ` Mark Lord
2006-03-21 19:33 ` Mark Lord
2006-03-21 19:35 ` Jens Axboe
2006-03-21 19:38 ` Jeff Garzik
2006-03-21 19:42 ` Jens Axboe [this message]
2006-03-21 19:43 ` James Bottomley
2006-03-21 19:46 ` Jens Axboe
2006-03-21 20:44 ` James Bottomley
2006-03-21 21:54 ` Benjamin Herrenschmidt
2006-03-21 19:31 ` Jens Axboe
2006-03-21 19:36 ` Mark Lord
2006-03-21 19:43 ` Jeff Garzik
2006-03-21 20:51 ` Mark Lord
2006-03-22 11:25 ` Tejun Heo
2006-03-22 14:52 ` Mark Lord
2006-03-21 1:15 ` Jeff Garzik
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=20060321194215.GP4285@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).