mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: linux-doc@vger.kernel.org, x86@kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Reinette Chatre <reinette.chatre@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	Babu Moger <Babu.Moger@amd.com>,
	linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>
Subject: [PATCH 2/4] Documentation: x86: Remove cdpl2 unspported statement and fix capitalisation
Date: Fri,  7 Jun 2019 16:14:07 +0100	[thread overview]
Message-ID: <20190607151409.15476-3-james.morse@arm.com> (raw)
In-Reply-To: <20190607151409.15476-1-james.morse@arm.com>

"L2 cache does not support code and data prioritization". This isn't
true, elsewhere the document says it can be enabled with the cdpl2
mount option.

While we're here, these sample strings have lower-case code/data,
which isn't how the kernel exports them.

Signed-off-by: James Morse <james.morse@arm.com>
---
 Documentation/x86/resctrl_ui.rst | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/Documentation/x86/resctrl_ui.rst b/Documentation/x86/resctrl_ui.rst
index 066f94e53418..638cd987937d 100644
--- a/Documentation/x86/resctrl_ui.rst
+++ b/Documentation/x86/resctrl_ui.rst
@@ -418,16 +418,22 @@ L3 schemata file details (CDP enabled via mount option to resctrl)
 When CDP is enabled L3 control is split into two separate resources
 so you can specify independent masks for code and data like this::
 
-	L3data:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
-	L3code:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
+	L3DATA:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
+	L3CODE:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
 
 L2 schemata file details
 ------------------------
-L2 cache does not support code and data prioritization, so the
-schemata format is always::
+CDP is supported at L2 using the 'cdpl2' mount option. The schemata
+format is either::
 
 	L2:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
 
+or
+
+	L2DATA:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
+	L2CODE:<cache_id0>=<cbm>;<cache_id1>=<cbm>;...
+
+
 Memory bandwidth Allocation (default mode)
 ------------------------------------------
 
-- 
2.20.1


  parent reply	other threads:[~2019-06-07 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 15:14 [PATCH 0/4] Documentation: x86: resctrl_ui.txt fixes and clarification James Morse
2019-06-07 15:14 ` [PATCH 1/4] Documentation: x86: Contiguous cbm isn't all X86 James Morse
2019-06-07 21:24   ` Fenghua Yu
2019-06-07 15:14 ` James Morse [this message]
2019-06-07 21:26   ` [PATCH 2/4] Documentation: x86: Remove cdpl2 unspported statement and fix capitalisation Fenghua Yu
2019-06-07 15:14 ` [PATCH 3/4] Documentation: x86: Clarify MBA takes MB as referring to mba_sc James Morse
2019-06-07 21:28   ` Fenghua Yu
2019-06-07 15:14 ` [PATCH 4/4] Documentation: x86: fix some typos James Morse
2019-06-07 21:29   ` Fenghua Yu
2019-06-20 20:16 ` [PATCH 0/4] Documentation: x86: resctrl_ui.txt fixes and clarification Jonathan Corbet

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=20190607151409.15476-3-james.morse@arm.com \
    --to=james.morse@arm.com \
    --cc=Babu.Moger@amd.com \
    --cc=corbet@lwn.net \
    --cc=fenghua.yu@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=x86@kernel.org \
    /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®