From: zhuyj <zyjzyj2000@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [E1000-devel] i40e card Tx resets
Date: Thu, 17 Mar 2016 10:20:49 +0800 [thread overview]
Message-ID: <56EA1481.80600@gmail.com> (raw)
In-Reply-To: <20160316143654.GD21307@oracle.com>
On 03/16/2016 10:36 PM, Sowmini Varadhan wrote:
> On (03/16/16 19:46), zhuyj wrote:
>
>> It is busy today. Tomorrow I will share the steps about pktgen tools.
> Ok. I can give that a try on my machine. It would be good to
> have some way to reproduce this as simply as possible, maybe
> we can take the discussion to netdev to see if others there
> have experienced this.
>
> --Sowmini
>
1. modprobe NET_PKTGEN
2. download the tar file and uncompress to any directory.
This tar file is from kernel. It is in samples/pktgen/
3. cd pktgen
4. pktgen_sample02_multiqueue.sh -i ethx -s size -t cpu_number
If size is set to a big number, the similar defect will occur.
Adjust this size to a appropriate number, my defect will not occur.
In the test, I found some types igb nic, such as i210, will work well no
matter the size is a big number.
some nic, such as 82580, it will not work well if the size is too big.
As such, I think my problem results from the hardware and the big size
triggers this problem.
I hope this can help us all.
Zhu Yanjun
next prev parent reply other threads:[~2016-03-17 2:20 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
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 [this message]
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=56EA1481.80600@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox