From: "John W. Linville" <linville@tuxdriver.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [patch 2.6.13] x86_64: implement dma_sync_single_range_for_{cpu,device}
Date: Tue, 30 Aug 2005 13:54:38 -0400 [thread overview]
Message-ID: <20050830175436.GB18998@tuxdriver.com> (raw)
In-Reply-To: <200508300314.35177.ak@suse.de>
On Tue, Aug 30, 2005 at 03:14:34AM +0200, Andi Kleen wrote:
> On Monday 29 August 2005 23:48, John W. Linville wrote:
> > I don't think calling the (apparently Intel-specific) swiotlb_*
> > functions would be an appropriate replacement.
>
> What I meant is that instead of the dumb implementation you did
> it would be better to implement it in swiotlb_* too and copy
> only the requested byte range there and then call these new
> functions from the x86-64 wrapper.
Thanks. That is more helpful than the previous message.
I was leery of disturbing the swiotlb_* API needlessly, especially
since that involves ia64 as well. But if you think that would be
better, then I'll work in that direction.
Patches to follow...
John
P.S. BTW, "dumb" is a term that is both subjective and perjorative.
IMHO, it is "dumb" to use the word "dumb" in public discourse...
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-08-30 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 20:09 [patch 2.6.13] x86_64: implement dma_sync_single_range_for_{cpu,device} John W. Linville
2005-08-29 20:54 ` Andi Kleen
2005-08-29 21:48 ` John W. Linville
2005-08-30 1:14 ` [discuss] " Andi Kleen
2005-08-30 17:54 ` John W. Linville [this message]
2005-08-30 17:58 ` [patch 2.6.13] swiotlb: add swiotlb_sync_single_range_for_{cpu,device} John W. Linville
2005-08-30 18:00 ` [patch 2.6.13] x86_64: implement 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=20050830175436.GB18998@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@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