linux-kernel - Re: [PATCH v2] sched: Micro optimization in pick_next_task() and in check_preempt

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Thu, 19 Dec 2019 20:16:17 +0000
From:   Kirill Tkhai <ktkhai@...tuozzo.com>
To:     Steven Rostedt <rostedt@...dmis.org>
CC:     Peter Zijlstra <peterz@...radead.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "juri.lelli@...hat.com" <juri.lelli@...hat.com>,
        "vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
        "dietmar.eggemann@....com" <dietmar.eggemann@....com>,
        "bsegall@...gle.com" <bsegall@...gle.com>,
        "mgorman@...e.de" <mgorman@...e.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] sched: Micro optimization in pick_next_task() and in
 check_preempt_curr()

On 19.12.2019 19:22, Steven Rostedt wrote:
> On Thu, 19 Dec 2019 19:08:05 +0300
> Kirill Tkhai <ktkhai@...tuozzo.com> wrote:
> 
>> Should I resend this as two patches, with your changes in a separate?
> 
> You don't have to, you can include multiple SOBs if a patch was written
> by two people.
> 
> But perhaps it will better to do so, that way people will know who to
> blame when the linker breaks ;-)
> 
> I'll send you a patch that you can apply just before your change. That
> may be the cleanest way.

Two small patches look better then one huge, so I prefer to send a patch
on top of yours :)