From: Alex Markuze <alex@weka.io>
To: hyunseok@ieee.org
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Performance issue with vmxnet3 pmd
Date: Wed, 13 Aug 2014 11:13:30 +0300 [thread overview]
Message-ID: <CAKfHP0W-toAPyb0zfR0zuczV6by=o0YBsR0Yt7CvT3ARanud2w@mail.gmail.com> (raw)
In-Reply-To: <CAAJNysJadBkP+X4MPCokPD95KoL92fGaUrar25Yajh3qDiTm5A@mail.gmail.com>
HI Guys, I will continue this thread.
On ubuntu 14.4 (Kernel 3.13) with DPDK 1.7 vmxnet3-usermap 1.2 doesn't compile.
>From the git it seems to have been updated 3 months ago.
Is this project going to be killed? And should I look for different
alternatives.
On Tue, Jul 8, 2014 at 6:08 PM, Hyunseok <hyunseok@ieee.org> wrote:
> Thomas,
>
> The last time I tried vmxnet3-usermap a couple of weeks ago, it did not
> compile against the latest kernel (3.11). Is it still the case? Or do you
> have the latest version which is compatible with newer kernels?
>
> Also, do you have any benchmark numbers with vmxnet3-usermap in any chance?
>
> Regards,
> -Hyunseok
>
>
>
>
> On Tue, Jul 8, 2014 at 3:05 AM, Thomas Monjalon <thomas.monjalon@6wind.com>
> wrote:
>
>> Hi,
>>
>> 2014-07-07 18:22, Hyunseok:
>> > I was testing l2-fwd with vmxnet3 pmd (included in dpdk).
>>
>> Have you tested vmxnet3-usermap (http://dpdk.org/doc/vmxnet3-usermap)?
>>
>> > The maximum forwarding rate I got from vmxnet3 pmd with l2fwd is only 2.5
>> > to 2.8 Gbps.
>>
>> It could be interesting to know your exact testing procedure with numbers
>> for
>> vmxnet3-usermap.
>>
>> Thanks
>> --
>> Thomas
>>
prev parent reply other threads:[~2014-08-13 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 22:22 Hyunseok
2014-07-07 23:03 ` Patel, Rashmin N
2014-07-07 23:48 ` Hyunseok
2014-07-08 0:07 ` Patel, Rashmin N
2014-07-08 7:05 ` Thomas Monjalon
2014-07-08 15:08 ` Hyunseok
2014-08-13 8:13 ` Alex Markuze [this message]
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='CAKfHP0W-toAPyb0zfR0zuczV6by=o0YBsR0Yt7CvT3ARanud2w@mail.gmail.com' \
--to=alex@weka.io \
--cc=dev@dpdk.org \
--cc=hyunseok@ieee.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).