linux-kernel - Aw: Re: BUG: Wrong dma queue handling in ixp4 driver

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

Message-ID: <trinity-476a1417-ff29-42b6-8e14-6470cfbb788b-1469185837787@3capp-gmx-bs80>
Date:	Fri, 22 Jul 2016 13:10:37 +0200
From:	"Lino Sanfilippo" <LinoSanfilippo@....de>
To:	"Krzysztof Hałasa" <khalasa@...p.pl>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Aw: Re:  BUG: Wrong dma queue handling in ixp4 driver

Hi Krzysztof,

> 
> Not really: there is one pool for all ports, but each port uses
> a separate desc_tab (allocated from that pool).

right, but even then using a dma pool seems to be a bit of overhead
for only a few allocations. As far as I understood those pools are 
meant for hundrets or thousands of rather small chunks.

I dont want to criticise it though, since the code at this place is surely
 not wrong. 
My initial post was due to a misunderstanding of mine: I thought the 
third parameter of dma_pool_create() is the total allocation size of all
chunks (dont ask me how I came to this conclusion, I could not explain it now :/ ).

Regards,
Lino