From: Lawrence Brakmo <brakmo@fb.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: [RFC PATCH net-next] tcp: add NV congestion control
Date: Mon, 6 Jul 2015 22:40:17 +0000 [thread overview]
Message-ID: <D1C050BB.47A5%brakmo@fb.com> (raw)
In-Reply-To: <20150703.094704.283183007204034386.davem@davemloft.net>
On 7/3/15, 9:47 AM, "David Miller" <davem@davemloft.net> wrote:
>From: Lawrence Brakmo <brakmo@fb.com>
>Date: Thu, 2 Jul 2015 18:21:24 -0700
>
>> This is a request for comments.
>>
>> TCP-NV (New Vegas) is a major update to TCP-Vegas. An earlier version of
>> NV was presented at 2010's LPC (slides). It is a delayed based
>> congestion avoidance for the data center. This version has been tested
>> within a 10G rack where the HW RTTs are 20-50us.
>>
>> A description of TCP-NV, including implementation and experimental
>> results, can be found at:
>> http://www.brakmo.org/networking/tcp-nv/TCPNV.html
>>
>> The current version includes many module parameters to support
>> experimentation with the parameters.
>>
>> Signed-off-by: Lawrence Brakmo <lawrence@brakmo.org>
>
>I'm disappointed in the skb->cb[] size increase, like Eric. This
>severely negatively impacts everyone on every Linux system in the
>world, not just people using NV.
>
>The performance implications from increasing sk_buff by even 1 byte in
>size are absolutely non-trivial.
I will look into Neal¹s comment regarding using a union in the skb->cb[]
so I don¹t have to increase skb->cb[] size.
next prev parent reply other threads:[~2015-07-06 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 1:21 [RFC PATCH net-next] tcp: add NV congestion control Lawrence Brakmo
2015-07-03 5:00 ` Eric Dumazet
2015-07-03 16:37 ` David Miller
2015-07-03 17:10 ` Eric Dumazet
2015-07-03 16:47 ` David Miller
2015-07-06 22:40 ` Lawrence Brakmo [this message]
2015-07-03 17:10 ` Tom Herbert
2015-07-03 20:30 ` Neal Cardwell
2015-07-07 0:17 ` Lawrence Brakmo
2015-07-06 23:01 ` Lawrence Brakmo
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=D1C050BB.47A5%brakmo@fb.com \
--to=brakmo@fb.com \
--cc=Kernel-team@fb.com \
--cc=davem@davemloft.net \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.