netdev - Re: [PATCH net-next] tcp: do not pace pure ack packets

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:	Sat, 14 Feb 2015 22:45:18 +0200
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	Kenneth Klette Jonassen <kennetkl@....uio.no>,
	john fastabend <john.fastabend@...il.com>
Subject: Re: [PATCH net-next] tcp: do not pace pure ack packets

On Wed, Feb 4, 2015 at 4:31 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> From: Eric Dumazet <edumazet@...gle.com>
>
> When we added pacing to TCP, we decided to let sch_fq take care
> of actual pacing.
>
> All TCP had to do was to compute sk->pacing_rate using simple formula:
>
> sk->pacing_rate = 2 * cwnd * mss / rtt
>
> It works well for senders (bulk flows), but not very well for receivers
> or even RPC :
>
> cwnd on the receiver can be less than 10, rtt can be around 100ms, so we
> can end up pacing ACK packets, slowing down the sender.
> Really, only the sender should pace, according to its own logic.

[...]

> This patch is a combination of two patches we used for about one year at Google.

Wow, so what is the black box impact on systems running without the
fix, pacing works but also un-needed slow downs
are introduced, right?

Sounds to me as something we really want to push into -stable, isn't that?

Do you think we need to let the patch rot for a while in 3.20-rc or we
can do it right away?

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