mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Babu Moger <bmoger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
	Babu Moger <babu.moger@amd.com>,
	tony.luck@intel.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com
Cc: corbet@lwn.net, Dave.Martin@arm.com, james.morse@arm.com,
	x86@kernel.org, hpa@zytor.com, akpm@linux-foundation.org,
	paulmck@kernel.org, rdunlap@infradead.org, pmladek@suse.com,
	kees@kernel.org, arnd@arndb.de, fvdl@google.com,
	seanjc@google.com, pawan.kumar.gupta@linux.intel.com,
	xin@zytor.com, thomas.lendacky@amd.com, sohil.mehta@intel.com,
	jarkko@kernel.org, chang.seok.bae@intel.com, ebiggers@google.com,
	elena.reshetova@intel.com, ak@linux.intel.com,
	mario.limonciello@amd.com, perry.yuan@amd.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	peternewman@google.com, feng.tang@linux.alibaba.com
Subject: Re: [PATCH v12 06/10] fs/resctrl: Add user interface to enable/disable io_alloc feature
Date: Fri, 21 Nov 2025 08:04:08 -0600	[thread overview]
Message-ID: <73c0c936-9b5d-41ac-b028-d8d2009312a2@amd.com> (raw)
In-Reply-To: <65f94330-bd8f-436b-b02c-654f87e4bb29@intel.com>

Hi Reinette,

On 11/20/25 22:40, Reinette Chatre wrote:
> Hi Babu,
>
> On 11/20/25 10:35 AM, Babu Moger wrote:
>> Hi Reinette,
>>
>> On 11/12/25 18:57, Babu Moger wrote:
>>> AMD's SDCIAE forces all SDCI lines to be placed into the L3 cache portions
>>> identified by the highest-supported L3_MASK_n register, where n is the
>>> maximum supported CLOSID.
>>>
>>> To support AMD's SDCIAE, when io_alloc resctrl feature is enabled, reserve
>>> the highest CLOSID exclusively for I/O allocation traffic making it no
>>> longer available for general CPU cache allocation.
>>>
>>> Introduce user interface to enable/disable io_alloc feature and encourage
>>> users to enable io_alloc only when running workloads that can benefit from
>>> this functionality. On enable, initialize the io_alloc CLOSID with all
>>> usable CBMs across all the domains.
>>>
>>> Since CLOSIDs are managed by resctrl fs, it is least invasive to make
>>> "io_alloc is supported by maximum supported CLOSID" part of the initial
>>> resctrl fs support for io_alloc. Take care to minimally (only in error
>>> messages) expose this use of CLOSID for io_alloc to user space so that this
>>> is not required from other architectures that may support io_alloc
>>> differently in the future.
>>>
>>> When resctrl is mounted with "-o cdp" to enable code/data prioritization,
>>> there are two L3 resources that can support I/O allocation: L3CODE and
>>> L3DATA.  From resctrl fs perspective the two resources share a CLOSID and
>>> the architecture's available CLOSID are halved to support this.  The
>>> architecture's underlying CLOSID used by SDCIAE when CDP is enabled is the
>>> CLOSID associated with the CDP_CODE resource, but from resctrl's perspective
>>> there is only one CLOSID for both CDP_CODE and CDP_DATA. CDP_DATA is thus
>>> not usable for general (CPU) cache allocation nor I/O allocation. Keep the
>>> CDP_CODE and CDP_DATA I/O alloc status in sync to avoid any confusion to
>>> user space. That is, enabling io_alloc on CDP_CODE does so on CDP_DATA and
>>> vice-versa, and keep the I/O allocation CBMs of CDP_CODE and CDP_DATA in
>>> sync.
>>>
>>> Signed-off-by: Babu Moger <babu.moger@amd.com>
>>> ---
>>> v12: Minor format fix in resctrl.rst.
>>>        Added text about writable files in the info section.
>>>        Removed Reviewed-by tag from Reinette as there are some new text changes from Dave.
>> Only this patch needs "Reviewed-by" tag.
>>
>> Gentle reminder with upcoming holidays.
> Thank you. I just added my "Reviewed-by" tag.


Thank you.

>
>> Hoping this series will be queued for next merge window.
>>
> I think it is getting late for new things.
>

Oh, okay. The series is ready now. It’s a pretty simple one, so I’ll let 
you decide

Thanks

Babu



  reply	other threads:[~2025-11-21 14:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  0:57 [PATCH v12 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-11-13  0:57 ` [PATCH v12 01/10] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 02/10] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 03/10] x86,fs/resctrl: Detect io_alloc feature Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 04/10] x86,fs/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 05/10] fs/resctrl: Introduce interface to display "io_alloc" support Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 06/10] fs/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-11-20 18:35   ` Babu Moger
2025-11-21  4:40     ` Reinette Chatre
2025-11-21 14:04       ` Babu Moger [this message]
2025-11-21  4:41   ` Reinette Chatre
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 07/10] fs/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 08/10] fs/resctrl: Modify struct rdt_parse_data to pass mode and CLOSID Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 09/10] fs/resctrl: Introduce interface to modify io_alloc capacity bitmasks Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-13  0:57 ` [PATCH v12 10/10] fs/resctrl: Update bit_usage to reflect io_alloc Babu Moger
2025-11-22 15:48   ` [tip: x86/cache] " tip-bot2 for Babu Moger
2025-11-21 16:05 ` [PATCH v12 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Reinette Chatre
2025-11-21 17:27   ` Borislav Petkov

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=73c0c936-9b5d-41ac-b028-d8d2009312a2@amd.com \
    --to=bmoger@amd.com \
    --cc=Dave.Martin@arm.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=ebiggers@google.com \
    --cc=elena.reshetova@intel.com \
    --cc=feng.tang@linux.alibaba.com \
    --cc=fvdl@google.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=jarkko@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=perry.yuan@amd.com \
    --cc=peternewman@google.com \
    --cc=pmladek@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=reinette.chatre@intel.com \
    --cc=seanjc@google.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=xin@zytor.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®