From: Jose Gavine Cueto <pepedocs@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] kni vs. pmd
Date: Wed, 11 Dec 2013 07:12:24 +0800 [thread overview]
Message-ID: <CAJ5bv6EZ2tgMGjha+S=gxPw3Lxs2bkOy07oyLY_3zK03-wrHCw@mail.gmail.com> (raw)
Hi,
Correct me if I'm wrong, but in a high-level perspective I see that kni is
providing an option for applications to use their regular interfaces (e.g.
sockets) and abstracts the usage of pmds.
If this is somehow correct, are there any differences with regard to
performance benefits that can be brought between directly using pmd apis
and kni ?
I see that kni is easier to use, however at first (no code inspection)
look, it interfaces with the kernel which might have introduced some
overhead.
Cheers,
Pepe
--
To stop learning is like to stop loving.
next reply other threads:[~2013-12-10 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 23:12 Jose Gavine Cueto [this message]
2013-12-10 23:15 ` Jose Gavine Cueto
2013-12-12 23:07 ` Pashupati Kumar
2013-12-13 3:11 ` Jose Gavine Cueto
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='CAJ5bv6EZ2tgMGjha+S=gxPw3Lxs2bkOy07oyLY_3zK03-wrHCw@mail.gmail.com' \
--to=pepedocs@gmail.com \
--cc=dev@dpdk.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).