From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [RFC PATCH 0/2] Using virtio ethdev ports as non-root
Date: Fri, 6 Sep 2019 11:58:27 +0200 [thread overview]
Message-ID: <1567763909-307-1-git-send-email-david.marchand@redhat.com> (raw)
I managed to run testpmd as non-root with virtio ports after quite some
tries.
Sending a first RFC with the (not so big) changes that are required on
the DPDK side.
I will come with a little howto for the non-RFC series for people
interested in this, since I had to align quite some stars to make it
work.
--
David Marchand
David Marchand (2):
bus/pci: check IO permissions for UIO only
net/virtio: do not require IO permissions
drivers/bus/pci/bsd/pci.c | 5 +++++
drivers/bus/pci/linux/pci.c | 10 ++++++++++
drivers/net/virtio/virtio_ethdev.c | 8 ++------
3 files changed, 17 insertions(+), 6 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-09-06 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 9:58 David Marchand [this message]
2019-09-06 9:58 ` [dpdk-dev] [RFC PATCH 1/2] bus/pci: check IO permissions for UIO only David Marchand
2019-09-06 9:58 ` [dpdk-dev] [RFC PATCH 2/2] net/virtio: do not require IO permissions David Marchand
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=1567763909-307-1-git-send-email-david.marchand@redhat.com \
--to=david.marchand@redhat.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).