From: 康剑斌 <kjbmail@gmail.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: linux-kernel@vger.kernel.org, dan.j.williams@intel.com
Subject: Re: Can I/OAT DMA engineer access PCI MMIO space
Date: Tue, 03 May 2011 14:31:46 +0800 [thread overview]
Message-ID: <4DBFA152.8000709@gmail.com> (raw)
In-Reply-To: <1304395926.1589.27.camel@vkoul-udesk3>
>> yes, I had used 'ioremap_nocache' to map the IO memory and I can use
>> memcpy to copy data to this region. The async_tx should have been
>> correctly configured as
>> I can use aync_memcpy to copy data between different system memory address.
> Then you should be using memcpy_toio() and friends
>
Do you mean that if I have mapped the mmio, I can' use I/OAT dma
transfer to this region any more?
I can use memcpy to copy data, but it consumes lots of cpu as PCI access
is too slow.
If I can use i/oat dma and asyc_tx api to do the job, the performance
should be imporved.
Thanks
next prev parent reply other threads:[~2011-05-03 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 10:13 Can I/OAT DMA engineer access PCI MMIO space 康剑斌
2011-05-02 6:04 ` Koul, Vinod
2011-05-03 2:21 ` 康剑斌
2011-05-03 4:12 ` Koul, Vinod
2011-05-03 6:31 ` 康剑斌 [this message]
2011-05-03 15:58 ` Dan Williams
2011-05-05 8:45 ` 康剑斌
2011-05-05 15:11 ` Dan Williams
2011-05-03 16:05 ` Dan Williams
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=4DBFA152.8000709@gmail.com \
--to=kjbmail@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@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