From: Alexei Budankov <abudankov@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
Alexander Antonov <alexander.antonov@linux.intel.com>,
Riccardo Mancini <rickyman7@gmail.com>
Subject: Re: [PATCH v13 03/16] perf record: Introduce thread specific data array
Date: Fri, 11 Feb 2022 22:34:03 +0300 [thread overview]
Message-ID: <2f1688de-a96b-75b7-9172-ff7efd91b6ef@huawei.com> (raw)
In-Reply-To: <YgaUA4O2wvFFeeQJ@kernel.org>
On 11.02.2022 19:51, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jan 31, 2022 at 07:21:11PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Jan 31, 2022 at 06:39:39PM -0300, Arnaldo Carvalho de Melo escreveu:
>>> Some changes to reduce patch size, I have them in my local tree, will
>>> publish later.
>>
>> Its in perf/threaded at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
>>
>> Will continue tomorrow, testing it and checking the speedups on my
>> 5950x, I think the things I found so far can be fixed in follow up
>> patches, to make progress and have this merged sooner.
>>
>> I'll try and add committer notes with the test for some 'perf bench'
>> workload without/with parallel recording, something I missed in your
>> patch descriptions.
>
> Didn't manage to do that, but my considerations are minor at this point
> and plenty of informed people acked, reviewed, tested, so I'm not going
> to be the one to prevent this from going upstream.
>
> If we find problems (oh well), we'll fix it and progress.
>
> Thank you, Alexei Budankov, Jiri, Namhyung and Riccardo for working on
> making perf scale at the record phase for so long,
>
> I'm pushing this to perf/core, that should get into 5.18.
Please also accept my congratulations to
Alexey Bayduraev, Jiri, Namhyung and Riccardo Mancini
who made this happen.
Great work. Thanks!
Regards,
Alexei
next prev parent reply other threads:[~2022-02-11 19:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 18:34 [PATCH v13 00/16] Introduce threaded trace streaming for basic perf record operation Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 01/16] perf record: Introduce thread affinity and mmap masks Alexey Bayduraev
2022-01-31 21:00 ` Arnaldo Carvalho de Melo
2022-01-31 21:16 ` Arnaldo Carvalho de Melo
2022-02-01 11:46 ` Bayduraev, Alexey V
2022-01-31 22:03 ` Arnaldo Carvalho de Melo
2022-01-31 22:04 ` Arnaldo Carvalho de Melo
2022-04-04 22:25 ` Ian Rogers
2022-04-05 16:21 ` Bayduraev, Alexey V
2022-04-06 16:46 ` Ian Rogers
2022-01-17 18:34 ` [PATCH v13 02/16] tools lib: Introduce fdarray duplicate function Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 03/16] perf record: Introduce thread specific data array Alexey Bayduraev
2022-01-31 21:39 ` Arnaldo Carvalho de Melo
2022-01-31 22:21 ` Arnaldo Carvalho de Melo
2022-02-11 16:51 ` Arnaldo Carvalho de Melo
2022-02-11 16:52 ` Arnaldo Carvalho de Melo
2022-02-11 19:34 ` Alexei Budankov [this message]
2022-01-17 18:34 ` [PATCH v13 04/16] perf record: Introduce function to propagate control commands Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 05/16] perf record: Introduce thread local variable Alexey Bayduraev
2022-01-31 21:42 ` Arnaldo Carvalho de Melo
2022-01-31 21:45 ` Arnaldo Carvalho de Melo
2022-02-01 7:35 ` Bayduraev, Alexey V
2022-01-17 18:34 ` [PATCH v13 06/16] perf record: Stop threads in the end of trace streaming Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 07/16] perf record: Start threads in the beginning " Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 08/16] perf record: Introduce data file at mmap buffer object Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 09/16] perf record: Introduce bytes written stats Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 10/16] perf record: Introduce compressor at mmap buffer object Alexey Bayduraev
2022-01-31 21:56 ` Arnaldo Carvalho de Melo
2022-02-01 8:08 ` Bayduraev, Alexey V
2022-01-17 18:34 ` [PATCH v13 11/16] perf record: Introduce data transferred and compressed stats Alexey Bayduraev
2022-01-24 15:28 ` Arnaldo Carvalho de Melo
2022-01-24 16:39 ` Arnaldo Carvalho de Melo
2022-01-17 18:34 ` [PATCH v13 12/16] perf record: Introduce --threads command line option Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 13/16] perf record: Extend " Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 14/16] perf record: Implement compatibility checks Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 15/16] perf session: Load data directory files for analysis Alexey Bayduraev
2022-01-17 18:34 ` [PATCH v13 16/16] perf report: Output data file name in raw trace dump Alexey Bayduraev
2022-01-24 15:45 ` [PATCH v13 00/16] Introduce threaded trace streaming for basic perf record operation Jiri Olsa
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=2f1688de-a96b-75b7-9172-ff7efd91b6ef@huawei.com \
--to=abudankov@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.antonov@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.v.bayduraev@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 \
--cc=rickyman7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®