linux-kernel - Re: [net-next PATCH v5 0/3] net: TCP thin-stream latency-improving modifications

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: <20100218.154345.28706204.davem@davemloft.net>
Date:	Thu, 18 Feb 2010 15:43:45 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	apetlund@...ula.no
Cc:	netdev@...r.kernel.org, ilpo.jarvinen@...sinki.fi,
	eric.dumazet@...il.com, hannemann@...s.rwth-aachen.de,
	linux-kernel@...r.kernel.org, shemminger@...tta.com,
	william.allen.simpson@...il.com, damian@....rwth-aachen.de,
	ebiederm@...ssion.com, franco@...tsummer.de
Subject: Re: [net-next PATCH v5 0/3] net: TCP thin-stream latency-improving
 modifications

From: Andreas Petlund <apetlund@...ula.no>
Date: Thu, 18 Feb 2010 13:42:13 +0100

> This is a series of patches enabling non-intrusive, dynamically 
> triggered modifications that improve retransmission latencies 
> for thin streams.
> 
> The patch set was modified according to the feedback received.
> 
> Major change:
>       -Used bitfields to compact the nonagle variable
>        in the tcp_sock struct. nonagle, thin_lto and
>        thin_dupack is now contained in the same u8.
> 
> I decided to use bitfields to handle this as it is
> already done similarly in the tcp_options_received struct.
> 
> Also corrected some formatting issues.

All applied (I made sure the get the updated version of patch #3),
thanks a lot!
--
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/