netdev - Re: [PATCH net-next 0/8] tg3: Bugfixes and updates

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: <20101001.002628.267960834.davem@davemloft.net>
Date:	Fri, 01 Oct 2010 00:26:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mcarlson@...adcom.com
Cc:	netdev@...r.kernel.org, andy@...yhouse.net
Subject: Re: [PATCH net-next 0/8] tg3: Bugfixes and updates

From: "Matt Carlson" <mcarlson@...adcom.com>
Date: Thu, 30 Sep 2010 13:34:29 -0700

> This patchset implements some bugfixes, removes the 5724 device
> ID and introduces extended rx buffer rings.

All applied....

But really, I want to hear some real justification for a 2048 entry RX
ring at gigabit speeds.  I even think 512 is way too large for gigabit
parts.

Any machine that gets one of these newer 5717 parts does not need that
much queueing, and too deep queues tend to hurt locality and thus
performance.
--
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