From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Prashant Upadhyaya
<prashant.upadhyaya-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Which vmxnet3 pmd is to be used in dpdk 1.6.x?
Date: Mon, 10 Mar 2014 08:50:48 -0700 [thread overview]
Message-ID: <20140310085048.71a49faf@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C61F80094E7-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
On Mon, 10 Mar 2014 13:30:48 +0530
Prashant Upadhyaya <prashant.upadhyaya-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org> wrote:
> Hi Srini,
>
> Thanks, I could also make it work, thanks to your cue !
>
> Now then, this multi-segment not being supported in vmxnet3 driver is a big party-pooper for me. Unfortunately in my usecase, I do indeed make heavy use of multisegment buffers for sending out the data, so my usecase has failed and I will have to fix that.
>
> Also, can you please adivse how much is the max data rates you have been able to achieve with one vmxnet3 10G port.
>
> Thanks a lot for the advice once again.
>
> Regards
> -Prashant
I am integrating our driver with the 1.6.1 DPDK driver.
We support multi-segment, if you want I will backport that feature first.
next prev parent reply other threads:[~2014-03-10 15:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 15:23 Which vmxnet3 pmd is to be used in dpdk 1.6.x? Srinivasan J
[not found] ` <CAEbeQ+q2qZkufmZrHXd2r_JTq2wL-0=xm5-9ngqfqPqq8_A0eQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-05 14:28 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A50609C-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-03-05 15:10 ` David Marchand
[not found] ` <CALwxeUsV7NCgQBbL2XCSYm_RLx1tt5pMN_thbxnP_2D3ho4thw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-05 15:30 ` Prashant Upadhyaya
2014-03-06 6:50 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A506142-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-03-06 7:18 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A506166-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-03-07 3:38 ` Srinivasan J
[not found] ` <CAEbeQ+rpRdH-=WgLE_GC6dvcrFnLCq2p+gz7fPY4uZKR5mE5vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-07 5:13 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A5062FF-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-03-08 19:08 ` Srinivasan J
[not found] ` <CAEbeQ+oOx=UGPyLgpe-Uj0=vf1aCrKxEBhfAT_UOS13GrmQ5_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-10 8:00 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C61F80094E7-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-03-10 10:54 ` Prashant Upadhyaya
2014-03-10 15:50 ` Stephen Hemminger [this message]
[not found] ` <20140310085048.71a49faf-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-03-11 5:27 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C61F800965A-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-03-11 8:52 ` Prashant Upadhyaya
2014-03-21 8:11 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C61FB347581-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2014-05-06 5:48 ` Prashant Upadhyaya
2014-03-11 5:33 ` On vmxnet-pmd crash in DPDK 1.6.0r1 Daniel Kan
[not found] ` <010A5C29-965A-4DB3-BA3F-2525914016A0-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>
2014-03-11 6:20 ` Daniel Kan
[not found] ` <FA87CC34-EBB8-4F7B-8E1D-C440520969BA-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>
2014-03-11 6:29 ` Daniel Kan
[not found] ` <BF719725-C5BE-4CBA-9523-5293C04000BA-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>
2014-03-21 14:10 ` Thomas Monjalon
2014-03-05 14:55 ` 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=20140310085048.71a49faf@nehalam.linuxnetplumber.net \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=prashant.upadhyaya-pccXkzZloW5BDgjK7y7TUQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.