From: Alexander Duyck <alexander.duyck@gmail.com>
To: Pravin B Shelar <pshelar@nicira.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] net: Add STT support.
Date: Thu, 29 Jan 2015 19:46:17 -0800 [thread overview]
Message-ID: <54CAFE89.4090509@gmail.com> (raw)
In-Reply-To: <1422574156-1831-1-git-send-email-pshelar@nicira.com>
On 01/29/2015 03:29 PM, Pravin B Shelar wrote:
> Following patch series adds support for Stateless Transport
> Tunneling protocol.
> STT uses TCP segmentation offload available in most of NIC. On
> packet xmit STT driver appends STT header along with TCP header
> to the packet. For GSO packet GSO parameters are set according
> to tunnel configuration and packet is handed over to networking
> stack. This allows use of segmentation offload available in NICs
>
> The protocol is documented at
> http://www.ietf.org/archive/id/draft-davie-stt-06.txt
>
> I will send out OVS userspace patch on ovs-dev mailing list.
>
> Following are test results. All tests are done on net-next with
> STT and VXLAN kernel device without OVS.
>
> Single Netperf session:
> =======================
> VXLAN:
> CPU utilization
> - Send local: 1.26
> - Recv remote: 8.62
> Throughput: 4.9 Gbit/sec
> STT:
> CPU utilization
> - Send local: 1.01
> - Recv remote: 1.8
> Throughput: 9.45 Gbit/sec
>
> Five Netperf sessions:
> ======================
> VXLAN:
> CPU utilization
> - Send local: 9.7
> - Recv remote: 70 (varies from 60 to 80)
> Throughput: 9.05 Gbit/sec
> STT:
> CPU utilization
> - Send local: 5.85
> - Recv remote: 14
> Throughput: 9.47 Gbit/sec
>
What does the small packet or non-TCP performance look like for STT vs
VXLAN? My concern is that STT looks like it is a one trick pony since
all your numbers show is TCP TSO performance, and based on some of the
comments in your patches it seems like other protocols such as UDP are
going to suffer pretty badly due to things like the linearization overhead.
- Alex
next prev parent reply other threads:[~2015-01-30 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 23:29 [PATCH net-next v2 0/6] net: Add STT support Pravin B Shelar
2015-01-30 3:46 ` Alexander Duyck [this message]
2015-01-30 4:04 ` Pravin Shelar
2015-01-30 4:17 ` Tom Herbert
2015-01-30 5:03 ` Pravin Shelar
2015-01-30 18:44 ` Andy Gospodarek
2015-02-02 18:44 ` Pravin Shelar
2015-01-30 16:46 ` Rick Jones
2015-02-01 1:40 ` David Miller
2015-02-02 18:44 ` Pravin Shelar
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=54CAFE89.4090509@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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).