From: Bjorn Helgaas <helgaas@kernel.org>
To: "Arinzon, David" <darinzon@amazon.com>
Cc: "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>,
Alex Williamson <alex.williamson@redhat.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:05:45 -0500 [thread overview]
Message-ID: <20220805160545.GA1020364@bhelgaas> (raw)
In-Reply-To: <d42f195bffa444719065f4e84098fe0c@EX13D47EUB004.ant.amazon.com>
[+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?
>
> We're leaning towards the ioctl option, if there are no objections,
> we'd come up with an RFC.
> [1]: https://patchwork.kernel.org/project/kvm/patch/20171009025000.39435-1-aik@ozlabs.ru/
> [2]: https://lore.kernel.org/linux-pci/2b539df4c9ec703458e46da2fc879ee3b310b31c.camel@kernel.crashing.org/
> [3]: https://lore.kernel.org/lkml/20210429162906.32742-2-sdonthineni@nvidia.com/
>
> Thanks,
> David
next prev parent reply other threads:[~2022-08-05 16:05 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 [this message]
2022-08-05 17:26 ` Alex Williamson
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=20220805160545.GA1020364@bhelgaas \
--to=helgaas@kernel.org \
--cc=akiyano@amazon.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=darinzon@amazon.com \
--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).