DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: "Ding, HengX" <hengx.ding@intel.com>,
	"yongwang@vmware.com" <yongwang@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] testpmd could not start up with vmxnet3 port
Date: Wed, 23 Mar 2016 03:31:34 +0000	[thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E0320E103@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <6EBE0505FB6FBE47AB600802285284524B853B86@CDSMSX101.ccr.corp.intel.com>

It's a regression, vmxnet3 can work with dpdk2.2, but now it can't work well.
Yong,
Heng found that your patch may be the first one to break the function, could you check it? Thx.

Thanks
Qian

From: Ding, HengX
Sent: Wednesday, March 23, 2016 11:28 AM
To: yongwang@vmware.com
Cc: Xu, Qian Q; dev@dpdk.org
Subject: testpmd could not start up with vmxnet3 port

Testpmd will fail to start up with vmxnet3 port. You can reproduce this issue follow these steps:


1.       Right click your VM and click edit settings

2.       Click "Add..." button.

3.       Choose Ethernet Adapter and click next

4.       Choose vmxnet3 as the Adapter Type, and select a network connection. Click next and finish config.

5.       Add another vmxnet3 port to VM follow step 1-4.

6.       Compile dpdk, bind vmxnet3 port to igb_uio and run testpmd: ./x86_64-native-linuxapp-gcc/app/testpmd -c f -n 4 -- -i


Here is the  bisect result:
f598fd063bb17eba9310ff48164014d09f40c759 is the first bad commit
commit f598fd063bb17eba9310ff48164014d09f40c759
Author: Yong Wang <yongwang@vmware.com<mailto:yongwang@vmware.com>>
Date:   Tue Jan 12 18:08:35 2016 -0800

    vmxnet3: add Tx L4 checksum offload

    Support TCP/UDP checksum offload.

    Signed-off-by: Yong Wang <yongwang@vmware.com<mailto:yongwang@vmware.com>>
    Acked-by: Stephen Hemminger <stephen@networkplumber.org<mailto:stephen@networkplumber.org>>

:040000 040000 4524306879c4c0093ac54b0c66b8a8f895af8337 8e1473e7cc9052003abe6caae8e8b232810972d4 M      doc
:040000 040000 ad9cd888717dd976a43cfe05aaf33f3b83a2f7bc 9fbd6fefb95f67bb407bb9a7efcf39e707ab21a7 M      drivers

  reply	other threads:[~2016-03-23  3:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23  3:27 Ding, HengX
2016-03-23  3:31 ` Xu, Qian Q [this message]
2016-03-23  5:52   ` Yong Wang
2016-03-23 17:27     ` Vincent Li
2016-03-23  5:57   ` Yong Wang
2016-03-23  6:28     ` Ding, HengX
2016-03-23 15:55     ` Thomas Monjalon
2016-03-24  3:38       ` Yong Wang

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=82F45D86ADE5454A95A89742C8D1410E0320E103@shsmsx102.ccr.corp.intel.com \
    --to=qian.q.xu@intel.com \
    --cc=dev@dpdk.org \
    --cc=hengx.ding@intel.com \
    --cc=yongwang@vmware.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).