From: Grant Grundler <iod00d@hp.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, discuss@x86-64.org,
linux-ia64@vger.kernel.org, ak@suse.de, "Mallick,
Asit K" <asit.k.mallick@intel.com>
Subject: Re: [patch 2.6.13 0/6] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device}
Date: Fri, 23 Sep 2005 14:38:51 -0700 [thread overview]
Message-ID: <20050923213851.GA6242@esmail.cup.hp.com> (raw)
In-Reply-To: <20050923185021.GC6576@tuxdriver.com>
On Fri, Sep 23, 2005 at 02:50:23PM -0400, John W. Linville wrote:
> On Fri, Sep 23, 2005 at 11:27:26AM -0700, Luck, Tony wrote:
> > >> It should just go away once the GFP_DMA32 code is merged.
> > >
> > >Is that the plan? I suppose it makes sense.
>
> > I don't have a good (or in fact any) understanding of the impact
> > of GFP_DMA32 on ia64. People tell me it will all be good, but I'd
> > like to hear from someone running it.
>
> All the patches I saw were for x86_64. So, the impact on ia64 should
> be minimal... :-)
impact to arch/ia64 might be minimal. My understanding was
all the drivers that support 32-bit devices would need tweaks
to use GFP_DMA32 flag. Is this still the plan?
http://www.ussg.iu.edu/hypermail/linux/kernel/9901.3/0323.html
Most of what I've read in Andi's patch otherwise makes sense:
http://lwn.net/Articles/152337/
But I didn't see Andi suggest that swiotlb should go completely away.
thanks,
grant
next prev parent reply other threads:[~2005-09-23 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 18:27 [patch 2.6.13 0/6] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device} Luck, Tony
2005-09-23 18:50 ` John W. Linville
2005-09-23 21:38 ` Grant Grundler [this message]
2005-09-26 7:01 ` Andi Kleen
2005-09-26 21:01 ` [patch 2.6.14-rc2 0/5] " John W. Linville
2005-09-26 21:01 ` [patch 2.6.14-rc2 1/5] swiotlb: move from arch/ia64/lib to drivers/pci John W. Linville
2005-09-26 21:01 ` [patch 2.6.14-rc2 2/5] swiotlb: cleanup some code duplication cruft John W. Linville
2005-09-26 21:01 ` [patch 2.6.14-rc2 3/5] swiotlb: support syncing sub-ranges of mappings John W. Linville
2005-09-26 21:01 ` [patch 2.6.14-rc2 4/5] swiotlb: support syncing DMA_BIDIRECTIONAL mappings John W. Linville
2005-09-26 21:01 ` [patch 2.6.14-rc2 5/5] swiotlb: file header comments John W. Linville
2005-09-26 21:33 ` [patch 2.6.14-rc2 0/5] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device} Matthew Wilcox
2005-09-26 21:54 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 20:37 [patch 2.6.13 0/6] " Luck, Tony
2005-09-22 20:41 ` Christoph Hellwig
2005-09-23 18:22 ` John W. Linville
2005-09-23 18:31 ` Muli Ben-Yehuda
2005-08-30 18:09 [patch 2.6.13] swiotlb: add swiotlb_sync_single_range_for_{cpu,device} John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 0/6] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device} John W. Linville
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=20050923213851.GA6242@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=ak@suse.de \
--cc=asit.k.mallick@intel.com \
--cc=discuss@x86-64.org \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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