From: Jonathan Cameron <Jonathan.Cameron@Huawei.com> To: Brice Goglin <brice.goglin@gmail.com> Cc: <linux-mm@kvack.org>, <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <x86@kernel.org>, Keith Busch <keith.busch@intel.com>, <jglisse@redhat.com>, "Rafael J . Wysocki" <rjw@rjwysocki.net>, <linuxarm@huawei.com>, "Andrew Morton" <akpm@linux-foundation.org>, Dan Williams <dan.j.williams@intel.com>, Tao Xu <tao3.xu@intel.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Hanjun Guo <guohanjun@huawei.com>, Sudeep Holla <sudeep.holla@arm.com> Subject: Re: [PATCH V6 7/7] docs: mm: numaperf.rst Add brief description for access class 1. Date: Wed, 18 Dec 2019 14:37:25 +0000 [thread overview] Message-ID: <20191218143725.00002f6f@Huawei.com> (raw) In-Reply-To: <4cf4e790-cacb-b250-bf28-5ba540eb0dc7@gmail.com> On Wed, 18 Dec 2019 12:34:34 +0100 Brice Goglin <brice.goglin@gmail.com> wrote: > Le 16/12/2019 à 16:38, Jonathan Cameron a écrit : > > 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..327c0d72692d 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 0, takes the same form, but only includes values for CPU to > > +memory activity. > > > Shouldn't this be "class 1" here? > Good point. Jonathan > Both hunks look contradictory to me. > > Brice > >
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com> To: Brice Goglin <brice.goglin@gmail.com> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, linux-acpi@vger.kernel.org, Tao Xu <tao3.xu@intel.com>, x86@kernel.org, "Rafael J . Wysocki" <rjw@rjwysocki.net>, linux-kernel@vger.kernel.org, linuxarm@huawei.com, Keith Busch <keith.busch@intel.com>, linux-mm@kvack.org, jglisse@redhat.com, Sudeep Holla <sudeep.holla@arm.com>, Hanjun Guo <guohanjun@huawei.com>, Andrew Morton <akpm@linux-foundation.org>, Dan Williams <dan.j.williams@intel.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH V6 7/7] docs: mm: numaperf.rst Add brief description for access class 1. Date: Wed, 18 Dec 2019 14:37:25 +0000 [thread overview] Message-ID: <20191218143725.00002f6f@Huawei.com> (raw) In-Reply-To: <4cf4e790-cacb-b250-bf28-5ba540eb0dc7@gmail.com> On Wed, 18 Dec 2019 12:34:34 +0100 Brice Goglin <brice.goglin@gmail.com> wrote: > Le 16/12/2019 à 16:38, Jonathan Cameron a écrit : > > 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..327c0d72692d 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 0, takes the same form, but only includes values for CPU to > > +memory activity. > > > Shouldn't this be "class 1" here? > Good point. Jonathan > Both hunks look contradictory to me. > > Brice > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-18 14:37 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-16 15:38 [PATCH V6 0/7] ACPI: Support Generic Initiator proximity domains Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 1/7] ACPI: Support Generic Initiator only domains Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 2/7] arm64: " Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 3/7] x86: Support Generic Initiator only proximity domains Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 4/7] ACPI: Let ACPI know we support Generic Initiator Affinity Structures Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 5/7] ACPI: HMAT: Fix handling of changes from ACPI 6.2 to ACPI 6.3 Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 6/7] node: Add access1 class to represent CPU to memory characteristics Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-16 15:38 ` [PATCH V6 7/7] docs: mm: numaperf.rst Add brief description for access class 1 Jonathan Cameron 2019-12-16 15:38 ` Jonathan Cameron 2019-12-18 11:34 ` Brice Goglin 2019-12-18 11:34 ` Brice Goglin 2019-12-18 14:37 ` Jonathan Cameron [this message] 2019-12-18 14:37 ` Jonathan Cameron 2019-12-18 11:32 ` [PATCH V6 0/7] ACPI: Support Generic Initiator proximity domains Brice Goglin 2019-12-18 11:32 ` Brice Goglin 2019-12-18 14:50 ` Jonathan Cameron 2019-12-18 14:50 ` Jonathan Cameron 2019-12-20 21:40 ` Brice Goglin 2019-12-20 21:40 ` Brice Goglin 2020-01-02 15:27 ` Jonathan Cameron 2020-01-02 15:27 ` Jonathan Cameron 2020-01-02 21:37 ` Brice Goglin 2020-01-02 21:37 ` Brice Goglin 2020-01-03 10:09 ` Jonathan Cameron 2020-01-03 10:09 ` Jonathan Cameron 2020-01-03 12:18 ` Brice Goglin 2020-01-03 12:18 ` Brice Goglin 2020-01-03 13:08 ` Jonathan Cameron 2020-01-03 13:08 ` Jonathan Cameron
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=20191218143725.00002f6f@Huawei.com \ --to=jonathan.cameron@huawei.com \ --cc=akpm@linux-foundation.org \ --cc=brice.goglin@gmail.com \ --cc=dan.j.williams@intel.com \ --cc=guohanjun@huawei.com \ --cc=jglisse@redhat.com \ --cc=keith.busch@intel.com \ --cc=linux-acpi@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=rjw@rjwysocki.net \ --cc=sudeep.holla@arm.com \ --cc=tao3.xu@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.