linux-kernel - RE: PCIe EndPoint DMA driver with DMA Framework

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] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2016 11:40:00 +0000
From:	Bharat Kumar Gogada <bharat.kumar.gogada@...inx.com>
To:	Sinan Kaya <okaya@...eaurora.org>,
	Vinod Koul <vinod.koul@...el.com>
CC:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	nofooter <nofooter@...inx.com>,
	"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>
Subject: RE: PCIe EndPoint DMA driver with DMA Framework

Hi Vinod/kanya,

> On 6/13/2016 1:25 AM, Vinod Koul wrote:
> >> We are planning to write a PCIe EndPoint DMA driver with DMA
> >> Framework
> >> > targeting x86 machine.  (
> >> >
> "https://www.kernel.org/doc/Documentation/dmaengine/provider.txt")
> >> > Our DMA controller is part of PCIe End Point.  We are targeting to
> >> > measure PCIe performance with this Framework driver.
> >> >
> >> > But when I see DMA Framework drivers is kernel source "drivers/dma"
> >> > most of the drivers are platform drivers.
> > wrong, there are bunch of PCI X86 driver. Look closely dw, ioat etc
>
> I usually see endpoint specific DMA code to reside in the endpoint device
> driver not in the dmaengine directory.
>
> I think the main question is who the consumer of this DMA controller is like
> Vinod asked.
>
> If it is a general purpose DMA controller then dmaengine would be the right
> place.
>
> If it is specific to your endpoint, then it should be set up and used in your
> endpoint device driver.
>
Our DMA controller is specific to EP.

Thanks a lot kanya and vinod for the clarifications.

Bharat


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.