netdev - Re: de-indirect TCP congestion control

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]

Message-Id: <20180312.150406.1432667769589045118.davem@davemloft.net>
Date:   Mon, 12 Mar 2018 15:04:06 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     stephen@...workplumber.org
Cc:     eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: de-indirect TCP congestion control

From: Stephen Hemminger <stephen@...workplumber.org>
Date: Mon, 12 Mar 2018 11:45:52 -0700

> Since indirect calls are expensive, and now even more so, perhaps we should figure out
> a way to make the default TCP congestion control hooks into direct calls.
> 99% of the users just use the single CC module compiled into the kernel.

Who is this magic user with only one CC algorithm enabled in their
kernel?  I want to know who this dude is?

I don't think it's going to help much since people will have I think
at least two algorithms compiled into nearly everyone's tree.

Distributions will enable everything.

Google is going to have at least two algorithms enabled.

etc. etc. etc.

Getting rid of indirect calls is a fine goal, but the precondition you
are mentioning to achieve this doesn't seem practical at all.