linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-mm@kvack.org, linux-acpi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	rafael@kernel.org, Ingo Molnar <mingo@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	linuxarm@huawei.com, Dan Williams <dan.j.williams@intel.com>,
	Brice Goglin <Brice.Goglin@inria.fr>,
	Sean V Kelley <sean.v.kelley@linux.intel.com>,
	linux-api@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH v11 6/6] docs: mm: numaperf.rst Add brief description for access class 1.
Date: Mon, 28 Sep 2020 12:26:50 -0700	[thread overview]
Message-ID: <15e6f95b-adac-97e5-5ea9-4dd28ecf560d@infradead.org> (raw)
In-Reply-To: <20200928125235.446188-7-Jonathan.Cameron@huawei.com>

Hi--

On 9/28/20 5:52 AM, Jonathan Cameron wrote:
> 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>
> ---
>  v11: No change.
> 
>  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 4d69ef1de830..b89bb85eac75 100644
> --- a/Documentation/admin-guide/mm/numaperf.rst
> +++ b/Documentation/admin-guide/mm/numaperf.rst

> @@ -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.

-ETOOMANYCOMMAS.

Drop the first comma for sure. Maybe even the second one.

> +
>  ==========
>  NUMA Cache
>  ==========
> 

thanks.
-- 
~Randy


      reply	other threads:[~2020-09-28 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 12:52 [PATCH v11 0/6] ACPI: Support Generic Initiator proximity domains Jonathan Cameron
2020-09-28 12:52 ` [PATCH v11 1/6] ACPI: Support Generic Initiator only domains Jonathan Cameron
2020-09-28 12:52 ` [PATCH v11 2/6] x86: Support Generic Initiator only proximity domains Jonathan Cameron
2020-09-28 17:35   ` Borislav Petkov
2020-09-28 12:52 ` [PATCH v11 3/6] ACPI: Let ACPI know we support Generic Initiator Affinity Structures Jonathan Cameron
2020-09-28 12:52 ` [PATCH v11 4/6] ACPI: HMAT: Fix handling of changes from ACPI 6.2 to ACPI 6.3 Jonathan Cameron
2020-09-28 12:52 ` [PATCH v11 5/6] node: Add access1 class to represent CPU to memory characteristics Jonathan Cameron
2020-09-28 12:52 ` [PATCH v11 6/6] docs: mm: numaperf.rst Add brief description for access class 1 Jonathan Cameron
2020-09-28 19:26   ` Randy Dunlap [this message]

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=15e6f95b-adac-97e5-5ea9-4dd28ecf560d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=Brice.Goglin@inria.fr \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxarm@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=sean.v.kelley@linux.intel.com \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).