From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: jolsa@kernel.org, disgoel@linux.vnet.ibm.com, mpe@ellerman.id.au,
linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.vnet.ibm.com, rnsastry@linux.ibm.com,
kjain@linux.ibm.com, linux-kernel@vger.kernel.org,
srikar@linux.vnet.ibm.com, irogers@google.com
Subject: Re: [PATCH v2 0/4] Fix perf bench numa, futex and epoll to work with machines having #CPUs > 1K
Date: Sat, 9 Apr 2022 12:28:01 -0300 [thread overview]
Message-ID: <YlGmAd3LEh9He6Pg@kernel.org> (raw)
In-Reply-To: <20220406175113.87881-1-atrajeev@linux.vnet.ibm.com>
Em Wed, Apr 06, 2022 at 11:21:09PM +0530, Athira Rajeev escreveu:
> The perf benchmark for collections: numa, futex and epoll
> hits failure in system configuration with CPU's more than 1024.
> These benchmarks uses "sched_getaffinity" and "sched_setaffinity"
> in the code to work with affinity.
Applied 1-3, 4 needs some reworking and can wait for v5.19, the first 3
are fixes, so can go now.
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: irogers@google.com, maddy@linux.vnet.ibm.com,
srikar@linux.vnet.ibm.com, rnsastry@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
jolsa@kernel.org, kjain@linux.ibm.com,
disgoel@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/4] Fix perf bench numa, futex and epoll to work with machines having #CPUs > 1K
Date: Sat, 9 Apr 2022 12:28:01 -0300 [thread overview]
Message-ID: <YlGmAd3LEh9He6Pg@kernel.org> (raw)
In-Reply-To: <20220406175113.87881-1-atrajeev@linux.vnet.ibm.com>
Em Wed, Apr 06, 2022 at 11:21:09PM +0530, Athira Rajeev escreveu:
> The perf benchmark for collections: numa, futex and epoll
> hits failure in system configuration with CPU's more than 1024.
> These benchmarks uses "sched_getaffinity" and "sched_setaffinity"
> in the code to work with affinity.
Applied 1-3, 4 needs some reworking and can wait for v5.19, the first 3
are fixes, so can go now.
- Arnaldo
next prev parent reply other threads:[~2022-04-09 15:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 17:51 [PATCH v2 0/4] Fix perf bench numa, futex and epoll to work with machines having #CPUs > 1K Athira Rajeev
2022-04-06 17:51 ` Athira Rajeev
2022-04-06 17:51 ` [PATCH v2 1/4] tools/perf: Fix perf bench futex to correct usage of affinity for machines with " Athira Rajeev
2022-04-06 17:51 ` Athira Rajeev
2022-04-08 12:27 ` Srikar Dronamraju
2022-04-08 12:27 ` Srikar Dronamraju
2022-04-06 17:51 ` [PATCH v2 2/4] tools/perf: Fix perf bench epoll " Athira Rajeev
2022-04-06 17:51 ` Athira Rajeev
2022-04-06 17:51 ` [PATCH v2 3/4] tools/perf: Fix perf numa bench to fix " Athira Rajeev
2022-04-06 17:51 ` Athira Rajeev
2022-04-08 12:28 ` Srikar Dronamraju
2022-04-08 12:28 ` Srikar Dronamraju
2022-04-06 17:51 ` [PATCH v2 4/4] tools/perf: Fix perf bench numa testcase to check if CPU used to bind task is online Athira Rajeev
2022-04-06 17:51 ` Athira Rajeev
2022-04-08 12:26 ` Srikar Dronamraju
2022-04-08 12:26 ` Srikar Dronamraju
2022-04-09 6:29 ` Athira Rajeev
2022-04-09 6:29 ` Athira Rajeev
2022-04-09 15:20 ` Arnaldo Carvalho de Melo
2022-04-09 15:20 ` Arnaldo Carvalho de Melo
2022-04-11 13:54 ` Athira Rajeev
2022-04-11 13:54 ` Athira Rajeev
2022-04-07 0:35 ` [PATCH v2 0/4] Fix perf bench numa, futex and epoll to work with machines having #CPUs > 1K Ian Rogers
2022-04-07 0:35 ` Ian Rogers
2022-04-07 4:31 ` Athira Rajeev
2022-04-07 4:31 ` Athira Rajeev
2022-04-09 15:28 ` Arnaldo Carvalho de Melo [this message]
2022-04-09 15:28 ` Arnaldo Carvalho de Melo
2022-04-09 17:18 ` Arnaldo Carvalho de Melo
2022-04-09 17:18 ` Arnaldo Carvalho de Melo
2022-04-12 16:33 ` Athira Rajeev
2022-04-12 16:33 ` Athira Rajeev
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=YlGmAd3LEh9He6Pg@kernel.org \
--to=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rnsastry@linux.ibm.com \
--cc=srikar@linux.vnet.ibm.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.