Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] linux: tcp congestion and optimizations
Date: Mon, 17 Oct 2022 02:52:53 +0200	[thread overview]
Message-ID: <20221017005253.DpIUpHZwDmGeYYuOfLfRwab-AoGGZPZzWdzsE8LDiiQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39951@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

Closed issue by tetsumaki on void-packages repository

https://github.com/void-linux/void-packages/issues/39951

Description:
Hello everyone,

I've been using Void Linux for a long time now, and I found that the kernel was not optimized in an optimal way.

Void Linux uses the following settings:

```ini
net.ipv4.tcp_available_congestion_control = reno
net.core.default_qdisc = pfifo_fast
net.ipv4.tcp_congestion_control = reno
```

Most distributions (Rocky/Arch) use the following settings:

```ini
net.ipv4.tcp_available_congestion_control = cubic bbr
net.core.default_qdisc = fq_codel
net.ipv4.tcp_congestion_control = cubic
```

Alpine use the following settings:

```ini
net.ipv4.tcp_available_congestion_control = reno cubic
net.core.default_qdisc = pfifo_fast
net.ipv4.tcp_congestion_control = cubic
```

I think the best setting though is this (Rocky/Arch):

```ini
net.ipv4.tcp_available_congestion_control = cubic bbr
net.core.default_qdisc = fq_codel
net.ipv4.tcp_congestion_control = cubic
```

BBR is very good, but still in alpha, you have to give the user the choice to apply it.

Whatever happens, the kernel should be optimized, and the user should be allowed to change via sysctl.

The discussion is open (fq/fq_codel/sch_fq/cak, reno/bbr and others optimizations).

My english is not perfect ;)

Some links :
- https://github.com/google/bbr/blob/master/README
- https://wiki.archlinux.org/title/sysctl#Enable_BBR
- https://www.cyberciti.biz/cloud-computing/increase-your-linux-server-internet-speed-with-tcp-bbr-congestion-control/
- https://github.com/systemd/systemd/issues/9725
- https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/linux/trunk/config
- https://raw.githubusercontent.com/void-linux/void-packages/master/srcpkgs/linux5.19/files/x86_64-dotconfig

  parent reply	other threads:[~2022-10-17  0:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 12:45 [ISSUE] " tetsumaki
2022-10-14 15:39 ` sgn
2022-10-14 16:05 ` tetsumaki
2022-10-14 16:06 ` sgn
2022-10-14 16:25 ` tetsumaki
2022-10-14 16:31 ` sgn
2022-10-14 17:24 ` tetsumaki
2022-10-17  0:52 ` sgn [this message]
2022-10-17  0:52 ` sgn
2022-11-30 17:06 ` dtaht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221017005253.DpIUpHZwDmGeYYuOfLfRwab-AoGGZPZzWdzsE8LDiiQ@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).