From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Amit Singh Tomar <amitsinght@marvell.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
George Cherian <gcherian@marvell.com>,
"robh@kernel.org" <robh@kernel.org>,
"peternewman@google.com" <peternewman@google.com>,
Drew Fustini <dfustini@baylibre.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: resctrl2 - status
Date: Fri, 25 Aug 2023 11:58:08 -0700 [thread overview]
Message-ID: <dc4cd365-2a02-32a3-da78-7ba745877e97@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6083BC6B330FA7B7DFD3E76AFCE3A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Hi Tony,
On 8/25/2023 11:09 AM, Luck, Tony wrote:
>> Alternatively, can user space just take a "load all resctrl modules
>> and see what sticks" (even modules of different architectures since
>> a user space may want to be generic) approach?
>
> This mostly works. Except for the cases where different modules access
> the same underlying hardware, so can't be loaded together.
>
> Examples:
>
> rdt_l3_cat vs. rdt_l3_cdp - user needs to decide whether they want CDP or not.
> But this is already true ... they have to decide whether to pass the "-o cdp" option
> to mount.
>
> rdt_l3_mba vs. rdt_l3_mba_MBps - does the user want to control memory bandwidth
> with percentages, or with MB/sec values. Again the user already has to make this
> decision when choosing mount options.
>
>
> Maybe the "What resctrl options does this machine support?" question would be
> best answered with a small utility?
A user space utility or a kernel provided utility? If it is a user space utility
I think it would end up needing to duplicate what the kernel is required to do
to know if a particular feature is supported. It seems appropriate that this
could be a kernel utility that can share this existing information with user
space. resctrl already supports the interface for this via /sys/fs/resctrl/info.
fyi ... as with previous attempts to discuss this work I find it difficult
to discuss this work when you are selective about what you want to discuss/answer
and just wipe the rest. Through this I understand that I am not your target
audience.
Reinette
next prev parent reply other threads:[~2023-08-25 18:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 18:10 Luck, Tony
2023-08-25 17:47 ` Reinette Chatre
2023-08-25 18:09 ` Luck, Tony
2023-08-25 18:58 ` Reinette Chatre [this message]
2023-08-25 19:44 ` Luck, Tony
2023-08-25 20:20 ` Reinette Chatre
2023-08-25 20:54 ` Tony Luck
2023-08-25 23:08 ` Reinette Chatre
2023-08-26 1:11 ` Tony Luck
2023-08-28 14:50 ` Reinette Chatre
2023-09-06 18:21 ` Tony Luck
2023-09-08 18:08 ` Moger, Babu
2023-09-08 18:51 ` Luck, Tony
2023-09-08 21:35 ` Moger, Babu
2023-09-08 23:13 ` Tony Luck
2023-09-15 17:55 ` Drew Fustini
2023-09-18 10:44 ` Jonathan Cameron
2023-09-28 8:47 ` Peter Newman
2023-09-28 14:47 ` Luck, Tony
2023-09-29 9:38 ` Jonathan Cameron
2023-09-29 14:49 ` Drew Fustini
2023-09-15 17:16 ` James Morse
2023-09-15 20:38 ` Tony Luck
2023-09-21 0:21 ` Tony Luck
2023-09-19 12:53 ` Peter Newman
2023-09-19 16:40 ` Tony Luck
2023-08-29 10:23 ` Jonathan Cameron
2023-08-29 17:18 ` [EXT] " Amit Singh Tomar
2023-08-30 10:47 ` Jonathan Cameron
2023-09-15 17:16 ` James Morse
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=dc4cd365-2a02-32a3-da78-7ba745877e97@intel.com \
--to=reinette.chatre@intel.com \
--cc=amitsinght@marvell.com \
--cc=dfustini@baylibre.com \
--cc=fenghua.yu@intel.com \
--cc=gcherian@marvell.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®