From: Rick Jones <rick.jones2@hp.com>
To: Pravin Shelar <pshelar@nicira.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 0/6] net: Add STT support.
Date: Fri, 30 Jan 2015 08:46:04 -0800 [thread overview]
Message-ID: <54CBB54C.2050307@hp.com> (raw)
In-Reply-To: <CALnjE+pPh5nSvaLTnM-a0r2Gm6K8Hz5BU_CsiWzYmwijPCOgHg@mail.gmail.com>
On 01/29/2015 08:04 PM, Pravin Shelar wrote:
> On Thu, Jan 29, 2015 at 7:46 PM, Alexander Duyck
>> 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.
>>
>
> Current implementation is targeted for TCP workloads thats why I
> posted numbers with TCP, once UDP is optimized we can discuss UDP
> numbers. I am pretty sure the STT code can be optimized further
> specially for protocols other than TCP.
Not to pile-on or anything but indeed, there is much more to "TCP
workloads" than just bulk transfer (TCP_STREAM), which is precisely why
netperf was created oh so many years ago with its TCP_RR test to try to
replace ttcp, and why there are the methods of mine and others to do
aggregate PPS with it and other benchmarks.
Of course that comment applies not only to STT but also to any other
"get to link-rate" on a (single|smallnumberof) stream" change.
rick
next prev parent reply other threads:[~2015-01-30 16: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
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 [this message]
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=54CBB54C.2050307@hp.com \
--to=rick.jones2@hp.com \
--cc=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 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.