netdev - Re: RFC: Nagle latency tuning

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]

Date:	Mon, 22 Sep 2008 16:21:58 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	andi@...stfloor.org
Cc:	csnook@...hat.com, rick.jones2@...com, netdev@...r.kernel.org
Subject: Re: RFC: Nagle latency tuning

From: Andi Kleen <andi@...stfloor.org>
Date: Tue, 23 Sep 2008 01:24:28 +0200

> On Mon, Sep 22, 2008 at 04:13:23PM -0700, David Miller wrote:
> > From: Chris Snook <csnook@...hat.com>
> > Date: Mon, 22 Sep 2008 19:00:08 -0400
> > 
> > > Could you please point me to an example of a connection parameter
> > > that gets tuned and cached this way, so I can experiment with it?
> > 
> > You'll find tons of them in tcp_update_metrics().
> 
> IMHO that is actually obsolete because it does not take NAT
> into account. One IP does not necessarily share link characteristics.

It is not an invalid estimate even in the NAT case, and it's not
so illegal like TCP timewait recycling would be.

Andi, don't rain on the party for something that might be terribly
useful for many people.
--
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