From: Jiri Pirko <jpirko@redhat.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
eric.dumazet@gmail.com, bhutchings@solarflare.com,
shemminger@vyatta.com, fubar@us.ibm.com, andy@greyhouse.net,
tgraf@infradead.org, ebiederm@xmission.com, mirqus@gmail.com,
kaber@trash.net, greearb@candelatech.com, jesse@nicira.com,
fbl@redhat.com, benjamin.poirier@gmail.com, jzupka@redhat.com,
ivecera@redhat.com
Subject: Re: [patch net-next V8] net: introduce ethernet teaming device
Date: Mon, 14 Nov 2011 22:51:23 +0100 [thread overview]
Message-ID: <20111114215122.GC2250@minipsycho> (raw)
In-Reply-To: <4EC160B4.2040709@hp.com>
Mon, Nov 14, 2011 at 07:40:52PM CET, rick.jones2@hp.com wrote:
>On 11/12/2011 12:16 AM, Jiri Pirko wrote:
>>This patch introduces new network device called team. It supposes to be
>>very fast, simple, userspace-driven alternative to existing bonding
>>driver.
>
>What is the definition of "very" here - relative to bonding I
>presume? Are there actual performance figures available at this
>point? Something along the lines of test through both on the same
>hardware. I don't have HW on which to run myself but would be quite
>happy to help with say netperf command selection to demonstrate the
>difference between the two.
Rick, I will provide this.
But the simple fact how bond and team path differ suggests the results.
Stay tuned.
Jirka
>
>happy benchmrking,
>
>rick jones
next prev parent reply other threads:[~2011-11-14 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 8:16 [patch net-next V8] net: introduce ethernet teaming device Jiri Pirko
2011-11-13 21:09 ` David Miller
2011-11-14 17:31 ` Andy Gospodarek
2011-11-14 18:17 ` Eric Dumazet
2011-11-14 21:37 ` Jiri Pirko
2011-11-14 17:18 ` Andy Gospodarek
2011-11-14 21:35 ` Jiri Pirko
2011-11-16 16:30 ` Jiri Pirko
2011-11-14 18:40 ` Rick Jones
2011-11-14 21:51 ` Jiri Pirko [this message]
2011-11-15 1:56 ` Andy Gospodarek
2011-11-15 17:22 ` Rick Jones
2011-11-15 18:35 ` Eric Dumazet
2011-11-16 23:01 ` Michał Mirosław
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=20111114215122.GC2250@minipsycho \
--to=jpirko@redhat.com \
--cc=andy@greyhouse.net \
--cc=benjamin.poirier@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=fbl@redhat.com \
--cc=fubar@us.ibm.com \
--cc=greearb@candelatech.com \
--cc=ivecera@redhat.com \
--cc=jesse@nicira.com \
--cc=jzupka@redhat.com \
--cc=kaber@trash.net \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@vyatta.com \
--cc=tgraf@infradead.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;
as well as URLs for NNTP newsgroup(s).