From: Jay Rolette <rolette@infinite.io>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI performance is not what is claimed
Date: Thu, 20 Sep 2018 16:39:24 -0500 [thread overview]
Message-ID: <CADNuJVq47xJPKiLvWo3Xbu68WJ=0LpojB9=4aaDQ-+fcky9E2w@mail.gmail.com> (raw)
In-Reply-To: <20180920131630.345c17d2@xeon-e3>
On Thu, Sep 20, 2018 at 3:16 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Thu, 20 Sep 2018 15:02:53 -0500
> Jay Rolette <rolette@infinite.io> wrote:
>
> > On Thu, Sep 20, 2018 at 1:11 PM Stephen Hemminger <
> > stephen@networkplumber.org> wrote:
> >
> > > I wonder if KNI is claiming performance that was never measured on
> current
> > > CPU, OS, DPDK.
> > >
> > > With single stream and TCP testing on IXGBE (DPDK), I see lowest
> > > performance with KNI.
> > >
> > > Rx Tx
> > > KNI 3.2 Gbit/sec 1.3 Gbit/sec
> > > TAP 4.9 4.7
> > > Virtio 5.6 8.6
> > >
> > > Perhaps for 18.11 we should change documentation to remove language
> > > claiming
> > > better performance with KNI, and then plan for future deprecation?
> > >
> >
> > Do TAP and Virtio provide equivalent function to KNI? I can't speak for
> any
> > other products, but ours is dependent on KNI. The ability for control
> plane
> > applications to use normal Linux sockets with DPDK is key even if it
> isn't
> > performant.
> >
> > Hopefully the answer is "yes", in which case I'll happily port over to
> > using one of the faster mechanisms.
> >
> > Thanks,
> > Jay
>
> See:
>
> https://doc.dpdk.org/guides-17.11/howto/virtio_user_as_exceptional_path.html
Thanks. Looks like it's time to run some experiments again.
Jay
next prev parent reply other threads:[~2018-09-20 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 18:10 Stephen Hemminger
2018-09-20 20:02 ` Jay Rolette
2018-09-20 20:15 ` Stephen Hemminger
2018-09-20 20:16 ` Stephen Hemminger
2018-09-20 21:39 ` Jay Rolette [this message]
2018-09-21 8:30 ` Wang, Zhihong
2018-10-01 14:22 ` Honnappa Nagarahalli
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='CADNuJVq47xJPKiLvWo3Xbu68WJ=0LpojB9=4aaDQ-+fcky9E2w@mail.gmail.com' \
--to=rolette@infinite.io \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).