From: zimeiw <zimeiw@163.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Intel 82599ES send packets failed on dpdk-17.05.1 after traffic testing
Date: Tue, 22 Aug 2017 12:45:26 +0800 (CST) [thread overview]
Message-ID: <34912f2e.542d.15e084275cd.Coremail.zimeiw@163.com> (raw)
In-Reply-To: <2f4bdab7-9873-e293-26fd-36ef5f2d80a1@126.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 1401 bytes --]
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?
Thanks.
--
Best Regards,
zimeiw
\x16º&
©å\íyÊ&rtîx\v Ûm;Ó÷ÛM{Eën®sÚ¶\x18ZXµÎ×¢g'Eç\x1e÷~º&Î×¢g'\x18dÎ×¢g'ë}µïÍ;Ѽ¥Ù(®\x03è²×âÇ\bDLø×`¶\x0f°öáú+uëÝ¥Ù(®\x04î{mº\r´×½;ÓöûM´Ð!\x12M{\x1cj{â®ë\x01É!\x06 D4 íX«ºÁ')Þ^Ç\x1a·¬º[B,@\r\À\b,TN2\x16§-sµç(É×D#ÓLç^½Ú]à\TN0õÓ}7ÛEÒ\x10djwÕt^qè¯yÛ§z0]7Ó}´ÛM{ÓͶ×}8×d^qè¯y×ë¢k§z0q\v:k\x1eÓ\íyÊ&r}tßMöѼ¥¡Æ¥-Â+a\0D¶ç¤\x01éܯ*myÔLý¶\x02è6Ó^ôçN5ÛM4Ñ\x17z+Þuúèz-zË&¶íyÊ&r}tßMvßÖòÇ´×;^r\bDLø¿³9àßÓvÛdî{mº\r´×½wÓ|ûO4Ðc\x13ñéïzZ)yúè\x16§-sµç(ÉÑyÇ¢½ç_®¥¡Æ¥-\x1aÚ&j)å¡Æ¥v}tã}zë^õo+3²kiÓ¬íyÊ&rrè¶ë\x03¢h§¡\x17¥y«\x1eóÅ?¬"¶\x11\x1213âwm5ïO6Û]ôãm:ßõã_\x13¹í¶\x02è6Ó^õßN6Óí<ÓAk¢bâ\x1d©ájyb×;^r:#x#x0º)ízW('\x1dz÷ivJ+¸jxZXµÎ×¢g'\r«^Nç¶Ø\v ÛM{×}7ão´óM\fzË\x1aâ\x1d×7ß¿6Ûm·ßNµ+lzw^¨¥
©å\íyÊ&ruÌj)^®\b±éÝzf¢_7Õs\b0DëiÉ\bµé¢ÍæòHÄÏIêïzº'ILý:þÇ«½êÿÎ×¥µÔ^æ¬{Îw\x14þ¢÷¦mêö×m5Ý«vÓ^ôómµßN6Ñ'«©bÍæòFzº'^²É§üíz[]Eé^jǽÓQOì\v ºËuïm5é«vÓ^ôómµßN5á'«©bÍç(^µæÛM{ÓͶ×}8×
Ì\0æ±í5Î×¢g'¿³9àßÓvÛeÇ@õÛ½4Õ+ç-vduëÏ\x010j\x7fµë-¦g_\x18§½©bv+¶'ij¶¦z׫±p^ztáz·z÷ivJ+s\x1aYW«²*'Û]y>·yקqéb²Òâ²Ò\x1d\fðÊ¥«\
ë\x1a×b±Ë¬²*'±×¯vd¢¸\vËT˱Êâmèm¶ÿvd¢¸?_è¦Ø¨ÏÝzù[huëëz«²×ivJ+Ëç-
next prev parent reply other threads:[~2017-08-22 4:45 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 ` zimeiw [this message]
2017-08-22 7:49 ` [dpdk-dev] Intel 82599ES send packets failed on dpdk-17.05.1 after traffic testing Ferruh Yigit
2017-08-22 8:30 ` zimeiw
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=34912f2e.542d.15e084275cd.Coremail.zimeiw@163.com \
--to=zimeiw@163.com \
--cc=dev@dpdk.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).