linux-kernel - Re: What happened to CONFIG_TCP_NAGLE

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061201000030.1d8ba600@localhost.localdomain>
Date:	Fri, 1 Dec 2006 00:00:30 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	Phillip Susi <psusi@....rr.com>
Cc:	Matt Garman <matthew.garman@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: What happened to CONFIG_TCP_NAGLE_OFF?

> No, nagle was invented specifically for telnet.  Without nagle, every 

No it was general purpose. It fixes some extremely bad behaviour in TCP
with congestion well beyond the "telnet" behaviour.

> Things like mouse movements should not be sent over TCP at all.  UDP 
> makes a much better protocol for that kind of data since if a packet is 

UDP is rarely appropriate because it has no congestion control. There are
more appropriate protocols but they are rarely implemented so TCP
generally gets used.

> lost, there is no need to retransmit the same data; instead you just get 
> the next position update and don't care about where the mouse was during 
> the dropped packet.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/