netdev - Re: [net-next 10/12] bna: TX Queue Depth Fix

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: <CAA93jw7OrqruzEu4EzEubqFdKpLrkPN9ksh5SSqU5pVcSCjgcw@mail.gmail.com>
Date:	Tue, 30 Aug 2011 21:34:39 -0700
From:	Dave Taht <dave.taht@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Rasesh Mody <rmody@...cade.com>, davem@...emloft.net,
	netdev@...r.kernel.org, adapter_linux_open_src_team@...cade.com,
	Gurunatha Karaje <gkaraje@...cade.com>
Subject: Re: [net-next 10/12] bna: TX Queue Depth Fix

On Tue, Aug 30, 2011 at 9:24 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> Le mardi 30 août 2011 à 18:27 -0700, Rasesh Mody a écrit :
>> sk_buff unmap_array grows greater than 65536 (x2) with Tx ring of 65536.
>> Reducing TXQ depth and safe(max) acking of Tx events to 32768 (same as Rx).
>> Add defines for TX and RX queue depths.

I was happy at the 'reducing txq depth' portion of the email, then I
saw the value it was reduced to.

thx for commenting thusly...

> BNAD_MAX_Q_DEPTH is now defined but not used.
>
> BTW, 32768 slots in a RX queue is insane.

As that is many lunar distances worth of buffering... Are they
expecting transmissions from mars?


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html