From: Veaceslav Falico <vfalico@redhat.com>
To: Shawn Bohrer <sbohrer@rgmadvisors.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
tomk@rgmadvisors.com, netdev <netdev@vger.kernel.org>
Subject: Re: [net-next 0/3] Improve UDP multicast receive latency
Date: Tue, 1 Oct 2013 22:21:42 +0200 [thread overview]
Message-ID: <20131001202142.GA13888@redhat.com> (raw)
In-Reply-To: <1380656025-8847-1-git-send-email-sbohrer@rgmadvisors.com>
On Tue, Oct 01, 2013 at 02:33:42PM -0500, Shawn Bohrer wrote:
>The removal of the routing cache in 3.6 had impacted the latency of our
>UDP multicast workload. This patch series brings down the latency to
>what we were seeing with 3.4.
>
>Patch 1 "udp: Only allow busy read/poll on connected sockets" is mostly
>done for correctness and because it allows unifying the unicast and
>multicast paths when a socket is found in early demux. It can also
>improve latency for a connected multicast socket if busy read/poll is
>used.
>
>Patches 2&3 remove the fib lookups and restore latency for our workload
>to the pre 3.6 levels.
>
>Benchmark results from a netperf UDP_RR test:
>3.11 kernel 90596.44 transactions/s
>3.11 + series 91792.70 transactions/s
>
>Benchmark results from a fio 1 byte UDP multicast pingpong test
>(Multicast one way unicast response):
>3.11 kernel 12.647us RTT
>3.11 + series 12.233us RTT
>
>Shawn Bohrer (3):
> udp: Only allow busy read/poll on connected sockets
> udp: Add udp early demux
> net: ipv4 only populate IP_PKTINFO when needed
>
> include/net/ip.h | 2 +-
> include/net/sock.h | 2 +-
> include/net/udp.h | 1 +
> net/ipv4/af_inet.c | 1 +
> net/ipv4/ip_sockglue.c | 5 +-
> net/ipv4/raw.c | 2 +-
> net/ipv4/udp.c | 160 +++++++++++++++++++++++++++++++++++++++++------
> net/ipv6/udp.c | 5 +-
> 8 files changed, 150 insertions(+), 28 deletions(-)
>
>--
>1.7.7.6
>
>
>--
>
>---------------------------------------------------------------
>This email, along with any attachments, is confidential. If you
>believe you received this message in error, please contact the
>sender immediately and delete all copies of the message.
>Thank you.
It's not a good idea to send patches with that kind of footer, afaik.
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-01 20:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 19:33 [net-next 0/3] Improve UDP multicast receive latency Shawn Bohrer
2013-10-01 19:33 ` [net-next 1/3] udp: Only allow busy read/poll on connected sockets Shawn Bohrer
2013-10-01 20:44 ` Eric Dumazet
2013-10-01 19:33 ` [net-next 2/3] udp: Add udp early demux Shawn Bohrer
2013-10-01 20:12 ` Rick Jones
2013-10-01 22:26 ` Shawn Bohrer
2013-10-01 20:52 ` Eric Dumazet
2013-10-02 17:34 ` Shawn Bohrer
2013-10-02 18:09 ` Eric Dumazet
2013-10-02 20:35 ` Shawn Bohrer
2013-10-02 21:08 ` Eric Dumazet
2013-10-02 21:24 ` Shawn Bohrer
2013-10-02 21:38 ` Eric Dumazet
2013-10-03 17:39 ` Shawn Bohrer
2013-10-03 18:06 ` Eric Dumazet
2013-10-01 19:33 ` [net-next 3/3] net: ipv4 only populate IP_PKTINFO when needed Shawn Bohrer
2013-10-01 20:42 ` Eric Dumazet
2013-10-01 22:29 ` Shawn Bohrer
2013-10-01 20:21 ` Veaceslav Falico [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=20131001202142.GA13888@redhat.com \
--to=vfalico@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sbohrer@rgmadvisors.com \
--cc=tomk@rgmadvisors.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;
as well as URLs for NNTP newsgroup(s).