From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David Moore <dcm@MIT.EDU>
Cc: Jarod Wilson <jwilson@redhat.com>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fw-ohci: sync AT dma buffer before use
Date: Thu, 13 Mar 2008 00:24:10 +0100 [thread overview]
Message-ID: <47D8661A.4090809@s5r6.in-berlin.de> (raw)
In-Reply-To: <1205361349.19600.24.camel@aries.csail.mit.edu>
David Moore wrote:
> 1. The dma_sync should probably be done before the context_append
> because the controller could in theory start reading the data as soon as
> context_append is called right?
Yes, but its syncing is superfluous anyway, as mentioned in the other
post. *If* it is doing something for Jarod's setup, then only because
of side effects like memory barrier properties.
> 2. As an optimization, we should attempt to allocate the payload in the
> lower 32-bits of physical memory, to prevent extra memcopies on x86_64.
> I think this can be done by adding GFP_DMA32 to kmalloc where the
> payload was allocated in fw-cdev.c. There might be other places where
> we would benefit from GFP_DMA32 also. Of course, these optimizations
> are probably better saved for another patch.
I think so too. GFP_DMA32 would be appropriate on machines with
"software IOMMU" alias swiotlb.
Does GFP_DMA32 have adverse affects on machines with a real IOMMU?
--
Stefan Richter
-=====-==--- --== -==--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-03-12 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 21:43 Jarod Wilson
2008-03-12 22:35 ` David Moore
2008-03-12 23:24 ` Stefan Richter [this message]
2008-03-12 23:16 ` Stefan Richter
2008-03-13 1:11 ` Jarod Wilson
2008-03-13 8:49 ` Stefan Richter
2008-03-14 18:26 ` Jarod Wilson
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=47D8661A.4090809@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=dcm@MIT.EDU \
--cc=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®