DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Patel, Rashmin N" <rashmin.n.patel@intel.com>
To: Alex Markuze <alex@weka.io>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] VMXNET 3
Date: Tue, 26 Aug 2014 16:30:21 +0000	[thread overview]
Message-ID: <C68F1134885B32458704E1E4DA3E34F341A2A2C5@FMSMSX105.amr.corp.intel.com> (raw)
In-Reply-To: <CAKfHP0XcfOVBRka_eHwN=URypBKNHihQdrfn11OjKnr3Gptrgg@mail.gmail.com>

As far as I know, some of the us (developers) are submitting patches for the VMXNET3 driver, which is inside the DPDK package in librte_pmd_vmxnet3. I have used the other version for benchmarking a long back but as it was limited to Linux kernel and I found the librte_pmd_vmxnet3 version more elegant, I moved on to that one.

As far as performance is concerned, it's limited by the ESXi vSwitch and vmxnet3 backend code, so if you're looking for line rate at 10G, it's far down the road if vmxnet3 backend processing is optimized, but today you can achieve ~55-60% of 10G in a single VM using VMXNET3, although you if you want to consume more of 10G, you can try increasing number of VMs.

Thanks,
Rashmin

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
Sent: Tuesday, August 26, 2014 3:06 AM
To: dev@dpdk.org
Subject: [dpdk-dev] VMXNET 3

Hi
I'm looking for reasonable DPDK based solution in fully virtualised VMware environment.
From what I've seen there are several flavours of VMXNET 3 driver for dpdk not all of them seem to be alive - user map -last updated on may and doesn't compile on DPDK 1.7.

So to my question what is the state of the DPDK art in vmxnet drivers?
and what performance
could one expect over a 10/40/56G nic?

Thanks
Alex.

  reply	other threads:[~2014-08-26 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 10:05 Alex Markuze
2014-08-26 16:30 ` Patel, Rashmin N [this message]
2014-08-26 17:11 ` Patel, Rashmin N

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=C68F1134885B32458704E1E4DA3E34F341A2A2C5@FMSMSX105.amr.corp.intel.com \
    --to=rashmin.n.patel@intel.com \
    --cc=alex@weka.io \
    --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).