From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] perf record: adapt affinity to machines with #CPUs > 1K
Date: Mon, 25 Nov 2019 19:55:06 +0300 [thread overview]
Message-ID: <f9dd565f-a170-ce98-3ed0-23444bd8b89d@linux.intel.com> (raw)
In-Reply-To: <6c7de0f3-d75e-762d-f16e-10e9561c2afb@linux.intel.com>
On 25.11.2019 14:27, Alexey Budankov wrote:
>
> On 25.11.2019 14:21, Jiri Olsa wrote:
>> On Mon, Nov 25, 2019 at 02:13:20PM +0300, Alexey Budankov wrote:
>>> On 25.11.2019 12:42, Jiri Olsa wrote:
>>>> On Mon, Nov 25, 2019 at 09:08:57AM +0300, Alexey Budankov wrote:
>>>>
>>>> SNIP
>>>>
>>>>> -static void perf_mmap__setup_affinity_mask(struct mmap *map, struct mmap_params *mp)
>>>>> +static int perf_mmap__setup_affinity_mask(struct mmap *map, struct mmap_params *mp)
>>>>> {
>>>>> - CPU_ZERO(&map->affinity_mask);
>>>>> + map->affinity_mask.nbits = cpu__max_cpu();
>>>>> + map->affinity_mask.bits = bitmap_alloc(map->affinity_mask.nbits);
>>>>> + if (!map->affinity_mask.bits)
>>>>> + return -1;
>>>>> +
>>>>> if (mp->affinity == PERF_AFFINITY_NODE && cpu__max_node() > 1)
>>>>> build_node_mask(cpu__get_node(map->core.cpu), &map->affinity_mask);
>>>>> else if (mp->affinity == PERF_AFFINITY_CPU)
>>>>> - CPU_SET(map->core.cpu, &map->affinity_mask);
>>>>> + set_bit(map->core.cpu, map->affinity_mask.bits);
>>>>> +
>>>>> + return 0;
>>>>> }
>>>>>
>>>>> +#define MASK_SIZE 1023
>>>>> int mmap__mmap(struct mmap *map, struct mmap_params *mp, int fd, int cpu)
>>>>> {
>>>>> + char mask[MASK_SIZE + 1] = {0};
>>>>
>>>> does this need to be initialized?
>>>
>>> This is to make sure the message is zero terminated for vfprintf call()
>>
>> hum AFAICS it's used only in bitmap_scnprintf, which should
>> terminate the string properly
>
> If vfprintf() explicitly terminates output buffer with zero then
> the initialization above can be avoided.
Well, bitmap_scnprintf() returns the length of resulting string and
the length can be used to make zero termination in the buffer and
avoid mask initialization in the beginning.
~Alexey
>
>>
>> jirka
>>
>
> ~Alexey
>
prev parent reply other threads:[~2019-11-25 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 6:04 [PATCH v2 0/3] perf record: adapt NUMA awareness to machines with #CPUs > 1K Alexey Budankov
2019-11-25 6:06 ` [PATCH v2 1/3] tools bitmap: implement bitmap_equal() operation at bitmap API Alexey Budankov
2019-11-25 6:07 ` [PATCH v2 2/3] perf mmap: declare type for cpu mask of arbitrary length Alexey Budankov
2019-11-25 6:08 ` [PATCH v2 3/3] perf record: adapt affinity to machines with #CPUs > 1K Alexey Budankov
2019-11-25 9:42 ` Jiri Olsa
2019-11-25 11:13 ` Alexey Budankov
2019-11-25 11:21 ` Jiri Olsa
2019-11-25 11:27 ` Alexey Budankov
2019-11-25 16:55 ` Alexey Budankov [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=f9dd565f-a170-ce98-3ed0-23444bd8b89d@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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