netdev - Re: Socket buffer sizes with autotuning

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: <20080424.182857.83348182.davem@davemloft.net>
Date:	Thu, 24 Apr 2008 18:28:57 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	andi@...stfloor.org
Cc:	johnwheffner@...il.com, rick.jones2@...com, netdev@...r.kernel.org
Subject: Re: Socket buffer sizes with autotuning

From: Andi Kleen <andi@...stfloor.org>
Date: Fri, 25 Apr 2008 00:21:08 +0200

> That just means Linux does too much queueing by default.  Perhaps that
> should be fixed. On Ethernet hardware the NIC TX queue should be
> usually sufficient anyways I would guess. Do we really need the long
> qdisc queue too?

It is definitely an area that deserves attention and a real
investigation, that's for sure.

I spent a lot of time looking at the behavior in this area
while writing the NIU 10G driver.  As usual, I got distracted
before I could make any real experiments.

I'll try to get back to this if someone else doesn't beat
me to it.  We also have the TX multiqueue stuff to move
forward, and it's deeply related to these issues.
--
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