From: Mark Lord <liml@rtr.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: WARNING: at drivers/ata/libata-core.c:5988 ata_qc_issue()
Date: Fri, 25 Jan 2008 10:18:15 -0500 [thread overview]
Message-ID: <4799FDB7.8090601@rtr.ca> (raw)
In-Reply-To: <1201273261.3119.4.camel@localhost.localdomain>
James Bottomley wrote:
> On Thu, 2008-01-24 at 23:29 -0500, Mark Lord wrote:
>> Tejun Heo wrote:
>>> Mark Lord wrote:
>>> ..
>>>> Super! You've done a great job with this stuff, Tejun!
>>> Thanks but I can't really say nice things about how sata_sil24's
>>> qc_defer() is implemented or how we generally handle command deferring.
>>> We really need the control at the higher level - request_queue group.
>>> Oh well... I guess you guys will be talking about it over beer again
>>> soon. :-)
>> ..
>>
>> You too?
>>
>> Another one for those beers, is a way to tell the IOMMU code about
>> physical segment limitations -- so we can stop having to allocate
>> PRD tables 2X as big as necessary in drivers like sata_mv.
>
> If the IOMMU would observe the queue dma_boundary parameter, is that
> enough? (it is for the 64k PRD limit). If so, there are already
> patches in the works to solve this permanently. If not, could we get
> the requirements to see how it might be done?
..
That sounds like the right thing.
We just have ensure that:
1. single SG/PRD entries never cross a 64KB address boundary.
and these two then naturally follow for free:
2. single SG/PRD entries never exceed 64KB.
3. single SG/PRD entries never cross a 32-bit address boundary.
Are the patches going into 2.6.25 ?
How do we take advantage of them ?
Cheers
next prev parent reply other threads:[~2008-01-25 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 15:20 WARNING: at drivers/ata/libata-core.c:5988 ata_qc_issue() Mark Lord
2008-01-24 15:26 ` Tejun Heo
2008-01-24 15:56 ` Mark Lord
2008-01-24 23:36 ` Tejun Heo
2008-01-24 23:52 ` Mark Lord
2008-01-24 23:57 ` Tejun Heo
2008-01-25 0:02 ` Mark Lord
2008-01-25 0:07 ` Tejun Heo
2008-01-25 4:01 ` Mark Lord
2008-01-25 4:08 ` Tejun Heo
2008-01-25 4:29 ` Mark Lord
2008-01-25 4:36 ` Tejun Heo
2008-01-25 7:20 ` Jeff Garzik
2008-01-25 7:18 ` Jeff Garzik
2008-01-25 15:01 ` James Bottomley
2008-01-25 15:18 ` Mark Lord [this message]
2008-01-25 15:29 ` James Bottomley
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=4799FDB7.8090601@rtr.ca \
--to=liml@rtr.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--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).