[v7,6/6] docs: mm: numaperf.rst Add brief description for access class 1.

Message ID 20200713155600.2272743-7-Jonathan.Cameron@huawei.com
State Superseded
Headers show
  • ACPI: Support Generic Initiator proximity domains
Related show

Commit Message

Jonathan Cameron July 13, 2020, 3:56 p.m.
Try to make minimal changes to the document which already describes
access class 0 in a generic fashion (including IO initiatiors that
are not CPUs).

Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

 Documentation/admin-guide/mm/numaperf.rst | 8 ++++++++
 1 file changed, 8 insertions(+)



diff --git a/Documentation/admin-guide/mm/numaperf.rst b/Documentation/admin-guide/mm/numaperf.rst
index a80c3c37226e..a9b1a30f75af 100644
--- a/Documentation/admin-guide/mm/numaperf.rst
+++ b/Documentation/admin-guide/mm/numaperf.rst
@@ -56,6 +56,11 @@  nodes' access characteristics share the same performance relative to other
 linked initiator nodes. Each target within an initiator's access class,
 though, do not necessarily perform the same as each other.
+The access class "1" is used to allow differentiation between initiators
+that are CPUs and hence suitable for generic task scheduling, and
+IO initiators such as GPUs and CPUs.  Unlike access class 0, only
+nodes containing CPUs are considered.
 NUMA Performance
@@ -88,6 +93,9 @@  The latency attributes are provided in nanoseconds.
 The values reported here correspond to the rated latency and bandwidth
 for the platform.
+Access class 1, takes the same form, but only includes values for CPU to
+memory activity.
 NUMA Cache