From: "John W. Linville" <linville@tuxdriver.com>
To: Christoph Hellwig <hch@infradead.org>,
"Luck, Tony" <tony.luck@intel.com>,
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:22:35 -0400 [thread overview]
Message-ID: <20050923182233.GB6576@tuxdriver.com> (raw)
In-Reply-To: <20050922204155.GA5400@infradead.org>
On Thu, Sep 22, 2005 at 09:41:55PM +0100, Christoph Hellwig wrote:
> On Thu, Sep 22, 2005 at 01:37:46PM -0700, Luck, Tony wrote:
> > >Conduct some maintenance of the swiotlb code:
> > >
> > > -- Move the code from arch/ia64/lib to lib
> >
> > I agree that this code needs to move up out of arch/ia64, it is messy
> > that x86_64 needs to reach over and grab this from arch/ia64.
> >
> > But is "lib" really the right place for it to move to? Perhaps
> > a more logical place might be "drivers/pci/swiotlb/" since this
> > code is tightly coupled to pci?
>
> It should just go away once the GFP_DMA32 code is merged.
Is that the plan? I suppose it makes sense.
So, move it to driver/pci/swiotlb.c? Or just leave it where it is?
Either way, I'll redo the other patches to reflect the correct
location.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-09-23 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 20:37 [patch 2.6.13 0/6] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device} Luck, Tony
2005-09-22 20:41 ` Christoph Hellwig
2005-09-23 18:22 ` John W. Linville [this message]
2005-09-23 18:31 ` Muli Ben-Yehuda
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 18:27 Luck, Tony
2005-09-23 18:50 ` John W. Linville
2005-09-23 21:38 ` Grant Grundler
2005-09-26 7:01 ` Andi Kleen
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=20050923182233.GB6576@tuxdriver.com \
--to=linville@tuxdriver.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