From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next 0/6] net: make TCP preemptible
Date: Thu, 28 Apr 2016 18:18:39 -0300 [thread overview]
Message-ID: <20160428211839.GB2276@localhost.localdomain> (raw)
In-Reply-To: <1461821152-23200-1-git-send-email-edumazet@google.com>
On Wed, Apr 27, 2016 at 10:25:46PM -0700, Eric Dumazet wrote:
> Most of TCP stack assumed it was running from BH handler.
>
> This is great for most things, as TCP behavior is very sensitive
> to scheduling artifacts.
>
> However, the prequeue and backlog processing are problematic,
> as they need to be flushed with BH being blocked.
>
> To cope with modern needs, TCP sockets have big sk_rcvbuf values,
> in the order of 16 MB.
> This means that backlog can hold thousands of packets, and things
> like TCP coalescing or collapsing on this amount of packets can
> lead to insane latency spikes, since BH are blocked for too long.
And due to that, it may potentially lead to packet drops on NIC ring
buffers. Great, thanks Eric.
> It is time to make UDP/TCP stacks preemptible.
>
> Note that fast path still runs from BH handler.
>
> Eric Dumazet (6):
> tcp: do not assume TCP code is non preemptible
> tcp: do not block bh during prequeue processing
> dccp: do not assume DCCP code is non preemptible
> udp: prepare for non BH masking at backlog processing
> sctp: prepare for socket backlog behavior change
> net: do not block BH while processing socket backlog
>
> net/core/sock.c | 22 +++------
> net/dccp/input.c | 2 +-
> net/dccp/ipv4.c | 4 +-
> net/dccp/ipv6.c | 4 +-
> net/dccp/options.c | 2 +-
> net/ipv4/tcp.c | 6 +--
> net/ipv4/tcp_cdg.c | 20 ++++----
> net/ipv4/tcp_cubic.c | 20 ++++----
> net/ipv4/tcp_fastopen.c | 12 ++---
> net/ipv4/tcp_input.c | 126 +++++++++++++++++++----------------------------
> net/ipv4/tcp_ipv4.c | 14 ++++--
> net/ipv4/tcp_minisocks.c | 2 +-
> net/ipv4/tcp_output.c | 7 ++-
> net/ipv4/tcp_recovery.c | 4 +-
> net/ipv4/tcp_timer.c | 10 ++--
> net/ipv4/udp.c | 4 +-
> net/ipv6/tcp_ipv6.c | 12 ++---
> net/ipv6/udp.c | 4 +-
> net/sctp/inqueue.c | 2 +
> 19 files changed, 124 insertions(+), 153 deletions(-)
>
> --
> 2.8.0.rc3.226.g39d4020
>
prev parent reply other threads:[~2016-04-28 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 5:25 [PATCH net-next 0/6] net: make TCP preemptible Eric Dumazet
2016-04-28 5:25 ` [PATCH net-next 1/6] tcp: do not assume TCP code is non preemptible Eric Dumazet
2016-04-29 1:08 ` Eric Dumazet
2016-04-28 5:25 ` [PATCH net-next 2/6] tcp: do not block bh during prequeue processing Eric Dumazet
2016-04-28 5:25 ` [PATCH net-next 3/6] dccp: do not assume DCCP code is non preemptible Eric Dumazet
2016-04-28 5:25 ` [PATCH net-next 4/6] udp: prepare for non BH masking at backlog processing Eric Dumazet
2016-04-28 5:25 ` [PATCH net-next 5/6] sctp: prepare for socket backlog behavior change Eric Dumazet
2016-04-28 5:25 ` [PATCH net-next 6/6] net: do not block BH while processing socket backlog Eric Dumazet
2016-04-28 17:23 ` [PATCH net-next 0/6] net: make TCP preemptible Alexei Starovoitov
2016-04-28 17:41 ` Eric Dumazet
2016-04-28 17:51 ` Alexei Starovoitov
2016-04-28 18:04 ` Eric Dumazet
2016-04-28 21:18 ` Marcelo Ricardo Leitner [this message]
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=20160428211839.GB2276@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox