linux-kernel - Re: [PATCH 2/3] net: TCP thin linear timeouts

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-next>] [day] [month] [year] [list]

Date:	Fri, 30 Oct 2009 11:48:24 +0100
From:	apetlund@...ula.no
To:	"Rick Jones" <rick.jones2@...com>
Cc:	"Andreas Petlund" <apetlund@...ula.no>,
	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
	"Arnd Hannemann" <hannemann@...s.rwth-aachen.de>,
	"Eric Dumazet" <eric.dumazet@...il.com>,
	"Netdev" <netdev@...r.kernel.org>,
	"LKML" <linux-kernel@...r.kernel.org>, shemminger@...tta.com,
	"David Miller" <davem@...emloft.net>
Subject: Re: [PATCH 2/3] net: TCP thin linear timeouts

> Just how thin can a thin stream be when a thin stream is found thin? (to
the
> cadence of "How much wood could a woodchuck chuck if a woodchuck could
chuck wood?")
>
> Does a stream get so thin that a user's send could not be split into
four,
> sub-MSS TCP segments?

That was a nifty idea: Anti-Nagle the segments to be able to trigger fast
retransmissions. I think it is possible.

Besides using more resources on each send, this scheme will introduce the
need to delay parts of the segment, which is undesirable for
time-dependent applications (the intended target of the mechanisms).

I think it would be fun to implement and play around with such a mechanism
to see the effects.

Regards,
Andreas




--
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/