From: renaud sallantin <renaud.sallantin@gmail.com>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: Initial Spreading patch
Date: Thu, 14 May 2015 01:59:39 +0200 [thread overview]
Message-ID: <CAAvOmMuk4hRmgtF6R_WM5NVEh4mJ0LxJ82YdQ7P81dWtgUJE4g@mail.gmail.com> (raw)
In-Reply-To: <CAAvOmMsYfDLKS2jfhLsKbsMoLjCYyvCeexBrz7QR4JOzb8pL=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
Dear Dave,
A quick answer from a small paradise where I am ending my hollydays
(Internet is sadly not as efficient everywhere, and I am lucky to get your
email...) lets speak more about it next week !!!
Attached to this email, you can find our patch tested with Linux 3.13.8.
As you can see, we used a slightly modified version of the FQ scheduler
developed by Eric Dumazet.
We introduced two sysctl parameters to ease your tests:
- tcp_initial_spreading_rate_min (integer):
It corresponds to the minimal rate value computed by Initial Spreading.
Considering draft-sallantin-tcpm-initial-spreading-00,
tcp_initial_spreading_rate_min= MTU / T_Spreading
- tcp_initial_spreading_rate_debug (boolean):
When non-zero, a kernel log message will print the rate used by Initial
Spreading each time a TCP connection is opened.
Regards,
Renaud Sallantin
Dear all,
Following our last email,
some of you asked for our Initial Spreading implementation.
Attached to this email, you can find our patch tested with Linux 3.13.8.
As you can see, we used a slightly modified version of the FQ scheduler
developed by Eric Dumazet.
We introduced two sysctl parameters to ease your tests:
- tcp_initial_spreading_rate_min (integer):
It corresponds to the minimal rate value computed by Initial Spreading.
Considering draft-sallantin-tcpm-initial-spreading-00,
tcp_initial_spreading_rate_min= MTU / T_Spreading
- tcp_initial_spreading_rate_debug (boolean):
When non-zero, a kernel log message will print the rate used by Initial
Spreading each time a TCP connection is initialized
We hope that you will be able to try Initial Spreading and that you will
confirm the good results we obtained.
Your comments on the patch but also on the draft are more than welcome,
https://tools.ietf.org/html/draft-sallantin-tcpm-initial-spreading-00
Regards,
Renaud Sallantin
[-- Attachment #2: Type: text/html, Size: 2568 bytes --]
next parent reply other threads:[~2015-05-13 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAvOmMsYfDLKS2jfhLsKbsMoLjCYyvCeexBrz7QR4JOzb8pL=w@mail.gmail.com>
2015-05-13 23:59 ` renaud sallantin [this message]
2015-05-14 0:12 ` [Bloat] " renaud sallantin
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAvOmMuk4hRmgtF6R_WM5NVEh4mJ0LxJ82YdQ7P81dWtgUJE4g@mail.gmail.com \
--to=renaud.sallantin@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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