From: zimeiw <zimeiw@163.com>
To: "Ferruh Yigit" <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Intel 82599ES send packets failed on dpdk-17.05.1 after traffic testing
Date: Tue, 22 Aug 2017 16:30:01 +0800 (CST) [thread overview]
Message-ID: <4d5af588.9018.15e09100fb5.Coremail.zimeiw@163.com> (raw)
In-Reply-To: <d0b647a6-f63f-e26b-587b-9f14bfdaaff4@intel.com>
hi,
no use rte_eth_tx_prepare()?
I set txq_flags value as below, may it cause this issue?
.txq_flags = ~ETH_TXQ_FLAGS_NOXSUMS
--
Best Regards,
zimeiw
At 2017-08-22 15:49:56, "Ferruh Yigit" <ferruh.yigit@intel.com> wrote:
>On 8/22/2017 5:45 AM, zimeiw wrote:
>> hi,
>> My test env is dell T430 server, NIC is intel 82599ES.
>> I integrate my app with dpdk-17.05.1 version. after do some tcp traffic testing, app can receive packets from the 82599 NIC, but 82599 NIC send packets failed.
>> But my app with dpdk-17.02 works well.
>>
>>
>> If any change with ixgbe driver? or need some additional configuration for the NIC?
>
>tx_pkt_prepare added but it has been added on 17.02 which seems working
>for your case.
>
>Just to double check, are you using rte_eth_tx_prepare()?
>
>>
>>
>>
>> Thanks.
>>
>>
>> --
>>
>> Best Regards,
>> zimeiw
>>
>
next prev parent reply other threads:[~2017-08-22 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 7:26 [dpdk-dev] Why IVSHMEM was removed since 16.11 ? Furong
2017-08-08 9:05 ` Burakov, Anatoly
2017-08-22 4:45 ` [dpdk-dev] Intel 82599ES send packets failed on dpdk-17.05.1 after traffic testing zimeiw
2017-08-22 7:49 ` Ferruh Yigit
2017-08-22 8:30 ` zimeiw [this message]
2017-08-22 9:31 ` Ferruh Yigit
[not found] ` <14690343.b423.15e099a0469.Coremail.zimeiw@163.com>
[not found] ` <dc62a140-5dd3-a899-eff9-034d76a85854@intel.com>
[not found] ` <61108f0.c31e.15e0a35ef85.Coremail.zimeiw@163.com>
[not found] ` <0f7d45a5-12de-85bd-59d2-da212298c7d2@intel.com>
[not found] ` <1fb0a58e.cb3.15e0c93ac86.Coremail.zimeiw@163.com>
[not found] ` <78c407d1.4448.15e0d8bd37f.Coremail.zimeiw@163.com>
[not found] ` <a2eed349-ca31-2ba2-6458-7c701c02aa33@intel.com>
2017-08-23 11:47 ` zimeiw
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=4d5af588.9018.15e09100fb5.Coremail.zimeiw@163.com \
--to=zimeiw@163.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).