linux-kernel - Re: Can I/OAT DMA engineer access PCI MMIO space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DBFA152.8000709@gmail.com>
Date:	Tue, 03 May 2011 14:31:46 +0800
From:	康剑斌 <kjbmail@...il.com>
To:	"Koul, Vinod" <vinod.koul@...el.com>
CC:	linux-kernel@...r.kernel.org, dan.j.williams@...el.com
Subject: Re: Can I/OAT DMA engineer access PCI MMIO space


>> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/