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:	Tue, 9 Sep 2008 10:22:08 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Chris Snook <csnook@...hat.com>
Cc:	David Miller <davem@...emloft.net>, rick.jones2@...com,
	netdev@...r.kernel.org
Subject: Re: RFC: Nagle latency tuning

Hi.

On Tue, Sep 09, 2008 at 01:56:12AM -0400, Chris Snook (csnook@...hat.com) wrote:
> The easiest way to see the problem is to open a TCP socket to an echo 
> daemon on loopback, make a bunch of small writes totaling less than your 
> loopback MTU (accounting for overhead), and see how long it takes to get 
> your echoes.  You can probably do this with netcat, though I haven't 
> tried.  People don't expect loopback to have 40 ms latency when the box 
> is lightly loaded, so they'd really like to tweak that down when it's 
> hurting them.

Isn't Nagle without corking a very bad idea? Or you can not change the
application?

-- 
	Evgeniy Polyakov
--
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