From: Rick Jones <rick.jones2@hp.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: Jiri Pirko <jpirko@redhat.com>,
netdev@vger.kernel.org, davem@davemloft.net,
eric.dumazet@gmail.com, bhutchings@solarflare.com,
shemminger@vyatta.com, fubar@us.ibm.com, 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: Tue, 15 Nov 2011 09:22:47 -0800 [thread overview]
Message-ID: <4EC29FE7.70904@hp.com> (raw)
In-Reply-To: <20111115015616.GA25132@gospo.rdu.redhat.com>
> On most modern systems I suspect there will be little to no difference
> between bonding RX peformance and team performance.
>
> If there is any now, I suspect team and bond performance to be similar
> by the time team has to account for the corner-cases bonding has already
> resolved. :-)
>
> Benchmarks may prove otherwise, but I've yet to see Jiri produce
> anything. My initial testing doesn't demonstrate any measureable
> differences with 1Gbps interfaces on a multi-core, multi-socket system.
I wouldn't expect much difference in terms of bandwidth, I was thinking
the demonstration would be made in the area of service demand (CPU
consumed per unit work) and perhaps aggregate packets per second.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2011-11-15 17:22 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
2011-11-15 1:56 ` Andy Gospodarek
2011-11-15 17:22 ` Rick Jones [this message]
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=4EC29FE7.70904@hp.com \
--to=rick.jones2@hp.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=jpirko@redhat.com \
--cc=jzupka@redhat.com \
--cc=kaber@trash.net \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--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).