From: Alex Williamson <alex.williamson@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Arinzon, David" <darinzon@amazon.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Dagan, Noam" <ndagan@amazon.com>,
"Agroskin, Shay" <shayagr@amazon.com>,
"Brandes, Shai" <shaibran@amazon.com>,
"Kiyanovski, Arthur" <akiyano@amazon.com>,
"mk@semihalf.com" <mk@semihalf.com>,
Cornelia Huck <cohuck@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: vfio/pci - uAPI for WC
Date: Fri, 5 Aug 2022 11:26:50 -0600 [thread overview]
Message-ID: <20220805112650.5c13f9a3.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220805160545.GA1020364@bhelgaas>
On Fri, 5 Aug 2022 11:05:45 -0500
Bjorn Helgaas <helgaas@kernel.org> wrote:
> [+cc Alex, Cornelia, kvm, lkml (from "get_maintainer.pl drivers/vfio")
> and rewrapped for plain-text readability]
> On Thu, Aug 04, 2022 at 09:47:36AM +0000, Arinzon, David wrote:
> > Hi,
> >
> > There's currently no mechanism for vfio that exposes WC-related
> > operations (check if memory is WC capable, ask to WC memory) to user
> > space module entities, such as DPDK, for example.
> >
> > This topic has been previously discussed in [1], [2] and [3], but
> > there was no follow-up.
> >
> > This capability is very useful for DPDK, specifically to the DPDK
> > ENA driver that uses vfio-pci, which requires memory to be WC on the
> > TX path. Without WC, higher CPU utilization and performance
> > degradation are observed.
> >
> > In the above mentioned discussions, three options were suggested:
> > sysfs, ioctl, mmap extension (extra attributes).
> >
> > Was there any progress on this area? Is there someone who's looking
> > into this?
IIRC, much of the discussion was related to VM use cases on ARM and
they may have found alternate ways to do things more like x86. I'm not
aware of any current development towards a uAPI change to enable this.
Thanks,
Alex
prev parent reply other threads:[~2022-08-05 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c98f484bda1c44bbba73b0a67a2e4465@EX13D47EUB004.ant.amazon.com>
2022-08-04 9:47 ` vfio/pci - uAPI for WC Arinzon, David
2022-08-05 16:05 ` Bjorn Helgaas
2022-08-05 17:26 ` Alex Williamson [this message]
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=20220805112650.5c13f9a3.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=akiyano@amazon.com \
--cc=cohuck@redhat.com \
--cc=darinzon@amazon.com \
--cc=helgaas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mk@semihalf.com \
--cc=ndagan@amazon.com \
--cc=shaibran@amazon.com \
--cc=shayagr@amazon.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).