DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	kevin.traynor@redhat.com,  bruce.richardson@intel.com,
	hemant.agrawal@nxp.com, jerinj@marvell.com,
	 olivier.matz@6wind.com, maxime.coquelin@redhat.com
Subject: Re: [dpdk-dev] KNI alternatives
Date: Wed, 13 Jan 2021 09:10:33 -0800	[thread overview]
Message-ID: <CAOaVG14bS-Em3eww53EDSGQe-z5JZN-v7YJre5-H13ywCNzNtg@mail.gmail.com> (raw)
In-Reply-To: <1699913.2mAdEQRYyP@thomas>

Last time I tried.
Virtio user was as fast as KNI and consumed less cpu. Was seeing 10mpps
Tap was much slower. Like 1mpps.

Vpp uses virtio user.

Sorry for top post. Only have phone internet

On Wed, Jan 13, 2021, 9:06 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> Hi,
>
> As discussed today in the techboard meeting, KNI has probably
> better alternatives today without using an out-of-tree module.
> Virtio-user is a good candidate to replace KNI.
> What is the performance of TAP?
> Is there a way to leverage af_packet, af_xdp, or even pcap interfaces?
>
> In order to avoid using the KNI out-of-tree module,
> we should make the librte_kni compatible with an other interface.
> The big plan is then to move the KNI module out of the main DPDK repo,
> as we did for igb_uio.
>
> The first step of this plan might be to document pros & cons
> of the KNI alternatives inside the KNI documentation:
>         https://doc.dpdk.org/guides/prog_guide/kernel_nic_interface.html
>
> As a start, this doc should be better referenced:
>
> https://doc.dpdk.org/guides/howto/virtio_user_as_exceptional_path.html
>
> Note: I won't do this update myself, so feel free to step up!
> Thanks
>
>
>

  reply	other threads:[~2021-01-13 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 17:06 Thomas Monjalon
2021-01-13 17:10 ` Stephen Hemminger [this message]
2021-01-13 18:17   ` Igor Ryzhov
2021-01-13 18:45     ` Thomas Monjalon
2021-01-13 19:53       ` Igor Ryzhov
2021-01-14  5:50         ` Stephen Hemminger

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=CAOaVG14bS-Em3eww53EDSGQe-z5JZN-v7YJre5-H13ywCNzNtg@mail.gmail.com \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.traynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=olivier.matz@6wind.com \
    --cc=thomas@monjalon.net \
    /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).