DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] A Question about the necessity of DPDK VF for Ethernet PMDs
Date: Mon, 4 Feb 2019 11:30:11 +0000	[thread overview]
Message-ID: <CAD+H991KfTXwLSu4fco9W26m8LPqnQaYAG5k5yY-SUBjMigDDQ@mail.gmail.com> (raw)
In-Reply-To: <CAHLOa7RSXHGL8YpHXu5U1WOAh2uK0w9fnh8Eg_jB3dW5SdxKZg@mail.gmail.com>

On Mon, Feb 4, 2019 at 10:44 AM Rami Rosen <ramirose@gmail.com> wrote:

> Hi Alejandro,
>
> >Your concern is related to this thread
>
> Thanks for your reply, I was aware of this thread.
>
OK


> Still, I am not sure, in current kernels and currently available Ethernet
> DPDK PMDs about the answer to my queries (I don't think this mail thread
> gives info about it), like about what are the benefits of providing DPDK
> VFs,  is it mandatory in some use cases, and are there any advantage for
> using a DPDK PF/DPDK VF combination over using Kernel VF?
>
> That is an interesting discussion. I know there is some interest in this
case from OVS people, exactly for running an OVS instance inside a VM.
I can see other reasons:
   - when SRIOV is used by VMs, the slow path will always be faster (and
with lower latency) with DPDK.
   - When more VMs/containers than VFs, DPDK will allow to use SRIOV (for
higher priority VMs/containers) and vhost-user (for low-priority), and with
the low-priority being faster than through the kernel.
   - If SRIOV is not used by VMs, DPDK forwarding path using vhost-user
along with VF PMDs is faster than through the kernel.
   - Having the PF managed by user space could potentially mean faster VM
migration.
   - PF flow management, inserting/deleting flow rules, faster in user
space.


Regards,
>
> Rami Rosen
>
>
>

  reply	other threads:[~2019-02-04 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  7:43 Rami Rosen
2019-02-04 10:22 ` Alejandro Lucero
2019-02-04 10:44   ` Rami Rosen
2019-02-04 11:30     ` Alejandro Lucero [this message]
2019-02-04 12:19       ` Rami Rosen
2019-02-04 12:53         ` Alejandro Lucero

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=CAD+H991KfTXwLSu4fco9W26m8LPqnQaYAG5k5yY-SUBjMigDDQ@mail.gmail.com \
    --to=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    --cc=ramirose@gmail.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).