DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x?
Date: Wed, 5 Mar 2014 16:10:53 +0100	[thread overview]
Message-ID: <CALwxeUsV7NCgQBbL2XCSYm_RLx1tt5pMN_thbxnP_2D3ho4thw@mail.gmail.com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A50609C@GUREXMB01.ASIAN.AD.ARICENT.COM>

Hello Prashant,

On Wed, Mar 5, 2014 at 3:28 PM, Prashant Upadhyaya <
prashant.upadhyaya@aricent.com> wrote:

> Hi,
>
> I am also keen to know the answer to the question posted by Srini.
> The real question is -- is dpdk1.6.0r1 self-sufficient so that I don't
> need any extensions etc., or do I still need something from outside like
> the usermap kernel driver etc.
>
> Secondly, if I turn on all the debug options for the vmxnet3 pmd in the
> config file, 1.6.0r1 compilation runs into a problem and reports a function
> which is defined but not used.
>

Can you send your build error ? (maybe in a separate thread ?)


> I am trying to bring up DPDK inside Fedora18 Guest on ESXi -- when I used
> DPDK1.6.0r1 (without debug options turned on for vmxnet3 pmd) the igb_uio
> could take over the vmxnet3 NIC but I encountered a core dump in the dev
> init function for the vmxnet3 driver -- anybody encountered a similar issue
> ?
>

I encountered these problems as well.

- igb_uio module does not check if you disable vmxnet3-uio pmds, it will
always try to take over vmxnet3 devices.
I have a patch waiting in my working dir to cleanly disable vmxnet3-uio pmd.

- If you don't bind vmxnet3 devices to uio, but forget to enable
vmxnet3-usermap pmd (by specifiying -d librte_pmd_vmxnet3.so), then
internal vmxnet3-uio pmd will try to initialise and crash.
I did not look any deeper into this, the easiest way is to disable
vmxnet3-uio pmd + apply the patch I will send in a few minutes, as a first
workaround.


Regards,
-- 
David Marchand

  reply	other threads:[~2014-03-05 15:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 15:23 Srinivasan J
2014-03-05 14:28 ` Prashant Upadhyaya
2014-03-05 15:10   ` David Marchand [this message]
2014-03-05 15:30     ` Prashant Upadhyaya
2014-03-06  6:50     ` Prashant Upadhyaya
2014-03-06  7:18       ` Prashant Upadhyaya
2014-03-07  3:38         ` Srinivasan J
2014-03-07  5:13           ` Prashant Upadhyaya
2014-03-08 19:08             ` Srinivasan J
2014-03-10  8:00               ` Prashant Upadhyaya
2014-03-10 10:54                 ` Prashant Upadhyaya
2014-03-10 15:50                 ` Stephen Hemminger
2014-03-11  5:27                   ` Prashant Upadhyaya
2014-03-11  8:52                     ` Prashant Upadhyaya
2014-03-21  8:11                     ` Prashant Upadhyaya
2014-05-06  5:48                       ` Prashant Upadhyaya
2014-03-11  5:33                 ` [dpdk-dev] On vmxnet-pmd crash in DPDK 1.6.0r1 Daniel Kan
2014-03-11  6:20                   ` Daniel Kan
2014-03-11  6:29                     ` Daniel Kan
2014-03-21 14:10                       ` Thomas Monjalon
2014-03-05 14:55 ` [dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x? David Marchand

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=CALwxeUsV7NCgQBbL2XCSYm_RLx1tt5pMN_thbxnP_2D3ho4thw@mail.gmail.com \
    --to=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=prashant.upadhyaya@aricent.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).