From: Eric Dumazet <eric.dumazet@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Vijay Subramanian <subramanian.vijay@gmail.com>,
tcpdump-workers@lists.tcpdump.org, netdev@vger.kernel.org,
Matthew Vick <matthew.vick@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: twice past the taps, thence out to net?
Date: Fri, 16 Dec 2011 20:44:49 +0100 [thread overview]
Message-ID: <1324064689.2621.24.camel@edumazet-laptop> (raw)
In-Reply-To: <4EEB9D64.5080901@hp.com>
Le vendredi 16 décembre 2011 à 11:35 -0800, Rick Jones a écrit :
> I would *love* to. All my accessible igb-driven hardware is in an
> environment locked to the kernels already there :( Not that it makes it
> more possible for me to do it, but I suspect it does not require 30
> receivers to reproduce the dups with netperf TCP_STREAM. Particularly
> if the tx queue len is at 256 it may only take 6 or 8. In fact let me
> try that now...
>
> Yep, with just 8 destinations/concurrent TCP_STREAM tests from the one
> system one can still see the duplicates in the packet trace taken on the
> sender.
>
> Perhaps we can trouble the Intel guys to try to reproduce what I've seen?
>
I do have an igb card somewhere (in fact two dual ports), I'll do the
test myself !
Thanks
next prev parent reply other threads:[~2011-12-16 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 19:27 twice past the taps, thence out to net? Rick Jones
2011-12-15 0:58 ` Benjamin Poirier
2011-12-15 2:12 ` Vijay Subramanian
2011-12-15 17:43 ` Eric Dumazet
2011-12-15 18:32 ` Rick Jones
2011-12-15 18:44 ` Stephen Hemminger
2011-12-15 19:00 ` Eric Dumazet
2011-12-15 22:22 ` Rick Jones
2011-12-16 4:27 ` Eric Dumazet
2011-12-16 18:28 ` Jesse Brandeburg
2011-12-16 19:34 ` Eric Dumazet
2011-12-16 19:35 ` Rick Jones
2011-12-16 19:44 ` Eric Dumazet [this message]
2011-12-20 21:21 ` Wyborny, Carolyn
2011-12-15 18:54 ` Eric Dumazet
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=1324064689.2621.24.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=matthew.vick@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@vyatta.com \
--cc=subramanian.vijay@gmail.com \
--cc=tcpdump-workers@lists.tcpdump.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