linux-kernel - Re: [PATCH v3 fwctl 4/5] fwctl/bnxt

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20260205173346.GO2328995@ziepe.ca>
Date: Thu, 5 Feb 2026 13:33:46 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Pavan Chebbi <pavan.chebbi@...adcom.com>
Cc: Saeed Mahameed <saeedm@...dia.com>, michael.chan@...adcom.com,
	linux-kernel@...r.kernel.org, dave.jiang@...el.com,
	Jonathan.Cameron@...wei.com, gospo@...adcom.com,
	selvin.xavier@...adcom.com, leon@...nel.org,
	kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH v3 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device

On Thu, Feb 05, 2026 at 09:55:08AM +0530, Pavan Chebbi wrote:
> >
> > I find it a bit weird that the user needs to provide dma information and
> > structure ! this is supposed to be completely hidden by the driver to
> > simplify user space, the driver handles dma and access to HW, user space
> > just provides the commands and payloads and driver carries the input/output
> > for that user space.
> 
> This is so because our FW commands require optional DMA-able buffers.
> The application is only giving us the information that the driver
> should encapsulate in additional DMA-able buffers.
> There is a defined format for exchange of this information, because
> every command has a different number of additional buffers. Also the
> majority of the commands don't need any additional buffers.
> I hope this answers your next comments also.

Now I have questions, who allocates these buffers, how do they get DMA
mapped, who does all the copying??

Jason