Bug 2011952

Summary:	Add tuned selector for the number of CPU sockets in the system
Product:	Red Hat Enterprise Linux 9	Reporter:	Peter Rival <frival>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	ASSIGNED ---	QA Contact:	Robin Hack <rhack>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	bgray, ctatman, dshaks, jeder, jmario, jskarvad
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-07 07:28:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Rival 2021-10-07 19:22:01 UTC

We have a partner who is interested in being able to alter some system tunings based on whether the system is single- or multi-socket.  While it's possible right now using [script] it would seem more appropriate for this to be a first-class selector.  When we have more info on what kinds of tunings might be changed I'll add here, but I can certainly imagine scheduler settings might get tweaked depending on, say, NUMA latencies.

Comment 2 Jaroslav Škarvada 2023-03-09 14:42:18 UTC

We currently have cpuinfo_regex and uname_regex conditionals. I think you can currently do such query with the cpuinfo_regex and regex 'physical id\s+:\s+1' that IMHO should match on multisockets.

Maybe we could add some nicer alias for it, or maybe new class of conditionals?

Please provide more information.

Comment 3 RHEL Program Management 2023-04-07 07:28:01 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.