From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: danny.zhou@intel.com
Cc: dev@dpdk.org, john.r.fastabend@intel.com
Subject: Re: [dpdk-dev] bifurcated driver
Date: Wed, 05 Nov 2014 14:00:53 +0100 [thread overview]
Message-ID: <4163036.7ZLDrAu3iM@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C46444@IRSMSX102.ger.corp.intel.com>
Hi Danny,
2014-10-31 17:36, O'driscoll, Tim:
> Bifurcated Driver (Danny.Zhou@intel.com)
Thanks for the presentation of bifurcated driver during the community call.
I asked if you looked at ibverbs and you wanted a link to check.
The kernel module is here:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/infiniband/core
The userspace library:
http://git.kernel.org/cgit/libs/infiniband/libibverbs.git
Extract from Kconfig:
"
config INFINIBAND_USER_ACCESS
tristate "InfiniBand userspace access (verbs and CM)"
select ANON_INODES
---help---
Userspace InfiniBand access support. This enables the
kernel side of userspace verbs and the userspace
communication manager (CM). This allows userspace processes
to set up connections and directly access InfiniBand
hardware for fast-path operations. You will also need
libibverbs, libibcm and a hardware driver library from
<http://www.openfabrics.org/git/>.
"
It seems to be close to the bifurcated driver needs.
Not sure if it can solve the security issues if there is no dedicated MMU
in the NIC.
I feel we should sum up pros and cons of
- igb_uio
- uio_pci_generic
- VFIO
- ibverbs
- bifurcated driver
I suggest to consider these criterias:
- upstream status
- usable with kernel netdev
- usable in a vm
- usable for ethernet
- hardware requirements
- security protection
- performance
--
Thomas
next prev parent reply other threads:[~2014-11-05 12:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 9:22 [dpdk-dev] DPDK Community Conference Call - Friday 31st October O'driscoll, Tim
2014-10-24 15:05 ` Michael Marchetti
2014-10-24 15:22 ` O'driscoll, Tim
2014-10-31 15:34 ` O'driscoll, Tim
2014-10-31 17:36 ` O'driscoll, Tim
2014-11-01 12:59 ` Neil Horman
2014-11-01 14:05 ` Vincent JARDIN
2014-11-05 13:00 ` Thomas Monjalon [this message]
2014-11-05 15:14 ` [dpdk-dev] bifurcated driver Alex Markuze
2014-11-05 15:19 ` Alex Markuze
2014-11-05 22:19 ` Zhou, Danny
2014-11-05 22:48 ` Zhou, Danny
2014-11-06 1:30 ` Vincent JARDIN
2014-11-06 4:45 ` Zhou, Danny
2014-11-06 8:13 ` Alex Markuze
2014-11-06 9:10 ` Nicolas Dichtel
2014-11-24 11:57 ` Luke Gorrie
2014-11-24 13:38 ` Zhou, Danny
2014-11-20 7:17 ` [dpdk-dev] DPDK Community Conference Call - Friday 31st October Kevin Wilson
2014-11-20 13:13 ` O'driscoll, Tim
2014-11-20 17:02 ` Kevin Wilson
2014-11-20 23:26 ` O'driscoll, Tim
2014-11-21 10:54 ` Kevin Wilson
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=4163036.7ZLDrAu3iM@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=danny.zhou@intel.com \
--cc=dev@dpdk.org \
--cc=john.r.fastabend@intel.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).