From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kyle Meyer <kyle.meyer@hpe.com>
Cc: linux-kernel@vger.kernel.org, yury.norov@gmail.com,
linux@rasmusvillemoes.dk, mingo@redhat.com, peterz@infradead.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, russ.anderson@hpe.com,
dimitri.sivanich@hpe.com, steve.wahl@hpe.com
Subject: Re: [PATCH v2 2/2] sched/topology: Optimize topology_span_sane()
Date: Fri, 12 Apr 2024 17:25:26 +0300 [thread overview]
Message-ID: <ZhlEVoW6FJC6uBVE@smile.fi.intel.com> (raw)
In-Reply-To: <ZhhcPwFCgxDUhndo@DESKTOP-IR8JFSN.>
On Thu, Apr 11, 2024 at 04:55:11PM -0500, Kyle Meyer wrote:
> On Thu, Apr 11, 2024 at 01:38:46PM +0300, Andy Shevchenko wrote:
> > On Wed, Apr 10, 2024 at 04:33:11PM -0500, Kyle Meyer wrote:
...
> > > Since topology_span_sane() is called inside of for_each_cpu(), each
> > > pervious CPU has already been compared against every other CPU. The
> >
> > previous
>
> Thank you for pointing that out. Should I send an updated version or can
> a maintainer correct my mistake?
Depends on the maintainer. I'm not the one here, don't expect answer from me.
> > > current CPU only needs to be compared against higher-numbered CPUs.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-12 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 21:33 [PATCH v2 0/2] sched/topology: Optimize topology_span_sane() Kyle Meyer
2024-04-10 21:33 ` [PATCH v2 1/2] cpumask: Add for_each_cpu_from() Kyle Meyer
2024-04-15 11:50 ` Valentin Schneider
2024-04-10 21:33 ` [PATCH v2 2/2] sched/topology: Optimize topology_span_sane() Kyle Meyer
2024-04-11 10:38 ` Andy Shevchenko
2024-04-11 21:55 ` Kyle Meyer
2024-04-12 14:25 ` Andy Shevchenko [this message]
2024-04-13 17:42 ` Yury Norov
2024-04-15 11:50 ` Valentin Schneider
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=ZhlEVoW6FJC6uBVE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=dimitri.sivanich@hpe.com \
--cc=juri.lelli@redhat.com \
--cc=kyle.meyer@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yury.norov@gmail.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 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.