linux-kernel - Re: [PATCH v13 03/16] perf record: Introduce thread specific data array

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2f1688de-a96b-75b7-9172-ff7efd91b6ef@huawei.com>
Date:   Fri, 11 Feb 2022 22:34:03 +0300
From:   Alexei Budankov <abudankov@...wei.com>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexey Bayduraev <alexey.v.bayduraev@...ux.intel.com>
CC:     Jiri Olsa <jolsa@...hat.com>, Namhyung Kim <namhyung@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Andi Kleen <ak@...ux.intel.com>,
        "Adrian Hunter" <adrian.hunter@...el.com>,
        Alexander Antonov <alexander.antonov@...ux.intel.com>,
        Riccardo Mancini <rickyman7@...il.com>
Subject: Re: [PATCH v13 03/16] perf record: Introduce thread specific data
 array


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