lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250108205030.GU5556@nvidia.com>
Date: Wed, 8 Jan 2025 16:50:30 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Jeremy Linton <jeremy.linton@....com>
Cc: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Wathsala Vithanage <wathsala.vithanage@....com>,
	linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org,
	acpica-devel@...ts.linux.dev, linux-kernel@...r.kernel.org,
	lenb@...nel.org, robert.moore@...el.com, bhelgaas@...gle.com,
	wei.huang2@....com, honnappa.nagarahalli@....com,
	dhruv.tripathi@....com, rob.herring@....com
Subject: Re: [RFC 0/2] GENL interface for ACPI _DSM methods

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ