From: Jason Gunthorpe <jgg@nvidia.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
acpica-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
lenb@kernel.org, robert.moore@intel.com, bhelgaas@google.com,
wei.huang2@amd.com, honnappa.nagarahalli@arm.com,
dhruv.tripathi@arm.com, rob.herring@arm.com
Subject: Re: [RFC 0/2] GENL interface for ACPI _DSM methods
Date: Wed, 8 Jan 2025 16:50:30 -0400 [thread overview]
Message-ID: <20250108205030.GU5556@nvidia.com> (raw)
In-Reply-To: <d35924de-a560-40aa-a99d-7278009c5ff3@arm.com>
On Wed, Jan 08, 2025 at 01:59:35PM -0600, Jeremy Linton wrote:
> I'm under the impression this is a similar problem to cpu/irq/numa affinity
> where the driver/subsystem should be making the choice, but the user is
> provided the opportunity to override the defaults if they think there is
> benefit in their environment.
Which I think has been proven to have been a mistake. Instead over
overriding irq affinity though proc/irq under the covers of the driver
and hoping for the best the driver itself should have the opportinuty
to set the affinity for its objects directly.
Lets us not repeat this mistake with steering tag. The driver should
always be involved in this stuff, if you want it to work with DPDK
then go through the kernel driver that DPDK is running on top of (VFIO
or RDMA)
Jason
next prev parent reply other threads:[~2025-01-08 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 16:30 [RFC 0/2] GENL interface for ACPI _DSM methods Wathsala Vithanage
2025-01-06 16:30 ` [RFC PATCH 1/2] ACPI: Add support for invoking select _DSM methods from user space Wathsala Vithanage
2025-01-06 16:30 ` [RFC PATCH 2/2] PCI: Add generic netlink interface to TPH _DSM Wathsala Vithanage
2025-01-06 18:01 ` [RFC 0/2] GENL interface for ACPI _DSM methods Jonathan Cameron
2025-01-07 17:37 ` Jeremy Linton
2025-01-07 17:48 ` Jason Gunthorpe
2025-01-08 19:59 ` Jeremy Linton
2025-01-08 20:50 ` Jason Gunthorpe [this message]
2025-01-09 0:34 ` Wathsala Wathawana Vithanage
2025-01-09 13:38 ` Jason Gunthorpe
2025-01-09 13:42 ` Wathsala Wathawana Vithanage
2025-01-09 13:46 ` Jason Gunthorpe
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=20250108205030.GU5556@nvidia.com \
--to=jgg@nvidia.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=acpica-devel@lists.linux.dev \
--cc=bhelgaas@google.com \
--cc=dhruv.tripathi@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jeremy.linton@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rob.herring@arm.com \
--cc=robert.moore@intel.com \
--cc=wathsala.vithanage@arm.com \
--cc=wei.huang2@amd.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