From: Rick Jones <rick.jones2@hpe.com>
To: Tom Herbert <tom@herbertland.com>,
davem@davemloft.net, netdev@vger.kernel.org
Cc: kernel-team@fb.com
Subject: Re: [PATCH net-next 0/8] tou: Transports over UDP - part I
Date: Thu, 16 Jun 2016 11:10:23 -0700 [thread overview]
Message-ID: <5762EB8F.60801@hpe.com> (raw)
In-Reply-To: <1466099522-690741-1-git-send-email-tom@herbertland.com>
On 06/16/2016 10:51 AM, Tom Herbert wrote:
> Note that #1 is really about running a transport stack in userspace
> applications in clients, not necessarily servers. For servers we
> intend to modified the kernel stack in order to leverage existing
> implementation for building scalable serves (hence these patches).
Only if there is a v2 for other reasons... I assume that was meant to
be "scalable servers."
> Tested: Various cases of TOU with IPv4, IPv6 using TCP_STREAM and
> TCP_RR. Also, tested IPIP for comparing TOU encapsulation to IP
> tunneling.
>
> - IPv6 native
> 1 TCP_STREAM
> 8394 tps
TPS for TCP_STREAM? Is that Mbit/s?
> 200 TCP_RR
> 1726825 tps
> 100/177/361 90/95/99% latencies
To enhance the already good comprehensiveness of the numbers, a 1 TCP_RR
showing the effect on latency rather than aggregate PPS would be
goodness, as would a comparison of the service demands of the different
single-stream results.
CPU and NIC models would provide excellent context for the numbers.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2016-06-16 18:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:51 [PATCH net-next 0/8] tou: Transports over UDP - part I Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 1/8] net: Change SKB_GSO_DODGY to be a tx_flag Tom Herbert
2016-06-16 18:58 ` Alexander Duyck
2016-06-16 20:18 ` Tom Herbert
2016-06-16 20:33 ` Alexander Duyck
2016-06-17 22:33 ` Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 2/8] fou: Change ip_tunnel_encap to take net argument Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 3/8] tou: Base infrastructure for Transport over UDP Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 4/8] ipv4: Support TOU Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 5/8] tcp: Support for TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 6/8] ipv6: Support TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 7/8] tcp6: Support for TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 8/8] tou: Support for GSO Tom Herbert
2016-06-16 18:10 ` Rick Jones [this message]
2016-06-16 23:15 ` [PATCH net-next 0/8] tou: Transports over UDP - part I Hannes Frederic Sowa
2016-06-17 16:51 ` Tom Herbert
2016-06-21 16:56 ` Hannes Frederic Sowa
2016-06-18 3:09 ` David Miller
2016-06-18 3:52 ` Tom Herbert
2016-06-19 20:15 ` Hajime Tazaki
2016-06-20 3:07 ` David Miller
2016-06-20 15:13 ` Tom Herbert
2016-06-21 8:29 ` David Miller
2016-06-22 3:42 ` Jerry Chu
2016-06-22 4:06 ` David Ahern
2016-06-22 19:24 ` David Miller
2016-06-22 17:40 ` Tom Herbert
2016-06-22 19:23 ` David Miller
2016-06-25 15:56 ` Tom Herbert
2016-06-21 17:11 ` Hannes Frederic Sowa
2016-06-21 17:23 ` Tom Herbert
2016-06-22 22:15 ` Richard Weinberger
2016-06-22 22:56 ` Tom Herbert
2016-06-23 7:40 ` David Miller
2016-06-23 7:50 ` Richard Weinberger
2016-06-24 21:12 ` Tom Herbert
2016-06-24 21:36 ` Rick Jones
2016-06-24 21:46 ` Tom Herbert
2016-06-24 22:06 ` Rick Jones
2016-06-24 23:43 ` Tom Herbert
2016-06-25 0:01 ` Rick Jones
2016-06-25 16:22 ` Tom Herbert
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=5762EB8F.60801@hpe.com \
--to=rick.jones2@hpe.com \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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 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.