From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Avi Kivity <avi@scylladb.com>,
gleb@scylladb.com, corbet@lwn.net, dev@dpdk.org,
gregkh@linuxfoundation.org, mst@redhat.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
hjk@hansjkoch.de
Subject: Re: [dpdk-dev] [PATCH] vfio: Include No-IOMMU mode
Date: Wed, 02 Dec 2015 17:19:18 +0100 [thread overview]
Message-ID: <1473285.yZJWhu9CPo@xps13> (raw)
In-Reply-To: <1449070123.15753.35.camel@redhat.com>
Hi,
2015-12-02 08:28, Alex Williamson:
> On Mon, 2015-11-16 at 19:12 +0200, Avi Kivity wrote:
> > On 11/16/2015 07:06 PM, Alex Williamson wrote:
> > > FYI, this is now in v4.4-rc1 (the slightly modified v2 version). I want
> > > to give fair warning though that while we seem to agree on this idea, it
> > > hasn't been proven with a userspace driver port. I've opted to include
> > > it in this merge window rather than delaying it until v4.5, but I really
> > > need to see a user for this before the end of the v4.4 cycle or I think
> > > we'll need to revert and revisit for v4.5 anyway. I don't really have
> > > any interest in adding and maintaining code that has no users. Please
> > > keep me informed of progress with a dpdk port. Thanks,
> >
> > Thanks Alex. Copying the dpdk mailing list, where the users live.
> >
> > dpdk-ers: vfio-noiommu is a replacement for uio_pci_generic and
> > uio_igb. It supports MSI-X and so can be used on SR/IOV VF devices.
> > The intent is that you can use dpdk without an external module, using
> > vfio, whether you are on bare metal with an iommu, bare metal without an
> > iommu, or virtualized. However, dpdk needs modification to support this.
>
> Still no users for this that I'm aware of. I'm going to revert this in
> rc5 unless something changes. Thanks,
Removing needs for out-of-tree modules is a really nice achievement.
Yes, we (in the DPDK project) should check how to use this no-iommu VFIO
and to replace igb_uio.
I'm sorry we failed to catch your email and follow up.
Is it really too late? What is the risk of keeping it in Linux 4.4?
Advertising a new feature and removing it would be frustrating.
Have you tried this VFIO mode with DPDK?
How complex would be the patch to support it?
Thanks
next prev parent reply other threads:[~2015-12-02 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151028211309.14155.23867.stgit@gimli.home>
[not found] ` <1447693613.3946.258.camel@redhat.com>
2015-11-16 17:12 ` Avi Kivity
2015-12-02 15:28 ` Alex Williamson
2015-12-02 16:19 ` Thomas Monjalon [this message]
2015-12-02 16:31 ` Michael S. Tsirkin
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=1473285.yZJWhu9CPo@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alex.williamson@redhat.com \
--cc=avi@scylladb.com \
--cc=corbet@lwn.net \
--cc=dev@dpdk.org \
--cc=gleb@scylladb.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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).