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 12:53:53 +0000	[thread overview]
Message-ID: <CAD+H992aCAEcOv6K=B+t8DR7Vj90QCC4i_VSQchtq_yHeXK22Q@mail.gmail.com> (raw)
In-Reply-To: <CAHLOa7Qq97=QFyiF-WmAZbYE+bj_aDNxXcBC+Tx-8CDj9mrLjw@mail.gmail.com>

On Mon, Feb 4, 2019 at 12:19 PM Rami Rosen <ramirose@gmail.com> wrote:

> Hi, Alejandro,
>
> Thanks for you quick response.
>
> >When SRIOV is used by VMs, the slow path will always be faster (and
> >with lower latency) with DPDK.
>
> Yes, I am referring primarily to the SRIOV case in my question, when
> assigning PCI VF to a VM (most likely QEMU VM)
> Can you please explain what you mean about slow path in this context ?
>
>
First packets from a new VM connection will go through the slow path. With
SRIOV and assuming OVS offload, that implies the NIC sending the first
packet up to OVS through the PF and back down once OVS decides what to do
with that flow (including likely some flow rule offload).


> Not sure the OVS setup is relevant here, it seems (if I understand
> correctly) that VFIO is more commonly used in OVS setups,
> so this query is not relevant here (unless you use igb_uio which is less
> common)
>

I do not understand what you mean. VFIO is preferred because it is the
right way of doing IOMMU, and also the only way if OVS run as non-root.
If you have VMs using SRIOV, you need something like OVS in the host, and
here it comes the potential benefit of OVS DPDK, because any OVS required
action will likely be faster.


> According to
> http://docs.openvswitch.org/en/latest/intro/install/dpdk/
> "VFIO is prefered to the UIO driver when using recent versions of DPDK. "
> Regards,
> Rami Rosen
>
>
>
>

      reply	other threads:[~2019-02-04 12:54 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
2019-02-04 12:19       ` Rami Rosen
2019-02-04 12:53         ` Alejandro Lucero [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='CAD+H992aCAEcOv6K=B+t8DR7Vj90QCC4i_VSQchtq_yHeXK22Q@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).