From: zhuyj <zyjzyj2000@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [E1000-devel] i40e card Tx resets
Date: Wed, 16 Mar 2016 11:19:33 +0800 [thread overview]
Message-ID: <56E8D0C5.307@gmail.com> (raw)
In-Reply-To: <20160315105433.GC11063@oracle.com>
On 03/15/2016 06:54 PM, Sowmini Varadhan wrote:
> On (03/15/16 16:55), zhuyj wrote:
>> Sorry. I explain this in details.
>> I have an similar problem. At first, I think it is related with tso.
>> Then I made tests with pktgen tools and found that this similar
>> problem still occurred whether
>> tso is enabled or not.
>>
>> So I suggest to make tests with pktgen tools to exclude tso.
>>
> I realize that TSO might not be the root cause (Tushar also
> pointed that out) but might just be triggering the issue...
>
> I dont think we need pktgen at this point- it's quite easy
> to reproduce this on commodity Haswell servers, and by installing
> the rds-stress from the rpm below:
>
> http://public-yum.oracle.com/repo/OracleLinux/OL6/ofed_UEK/x86_64//getPackageSource/rds-tools-2.0.7-1.12.el6.src.rpm
>
> To run it, set up 2 nodes connected on i40e. I shall call them
> "client" and "server" though both will send traffic in the test
>
> Start the listener:
> server# modprobe rds-tcp
> server# rds-stress -r <server addr>
>
> Start the test:
>
> client# modprobe rds-tcp
> client# rds-stress -r <client addr> -s <server-addr> -q 256 -a 8192 -d16 -t16 -T30
>
> (all params are explained in the rds-stress man page)
>
> If you do this on ixgbe, you will see that the column for "tx+rx K/s"
> shows a steady throughput, whereas i40e numbers are bursty and low.
>
> Also, for i40e, you will see messages about TX hang on on the console.
>
> I think that, to find the root-cause, we need to see what is
> triggering the mdd error.
Hi,
Thanks for your reply.
Yesterday I made tests with rds-tools. It is very pity that I can not
reproduce my problem with rds-tools.
But with pktgen tools, I can reproduce this problem easily. And I found
that if I set the packet size to 17792 or less than this size,
this problem would not occur. But if I set the packet size > 17792, for
example 17793, my problem would occur.
As such, maybe the packet size triggers my problem. I am not sure that
the packet size will trigger your size.
Best Regards!
Zhu Yanjun
>
> Would be good if someone from Intel could provide some hints on
> how to do that (or try the above tests!)
>
> --Sowmini
next prev parent reply other threads:[~2016-03-16 3:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 21:43 [Intel-wired-lan] i40e card Tx resets Sowmini Varadhan
2016-03-15 6:12 ` [Intel-wired-lan] [E1000-devel] " zhuyj
2016-03-15 8:55 ` zhuyj
2016-03-15 10:54 ` Sowmini Varadhan
2016-03-16 3:19 ` zhuyj [this message]
2016-03-16 3:25 ` Sowmini Varadhan
2016-03-16 11:46 ` zhuyj
2016-03-16 14:36 ` Sowmini Varadhan
2016-03-17 2:20 ` zhuyj
2016-03-17 2:29 ` zhuyj
2016-03-17 18:56 ` Sowmini Varadhan
2016-03-17 19:28 ` Jesse Brandeburg
2016-03-17 19:41 ` Sowmini Varadhan
2016-03-18 11:08 ` zhuyj
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=56E8D0C5.307@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=intel-wired-lan@osuosl.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 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.