linux-kernel - Re: [PATCH v2 02/13] sched/fair: Consistent use of prev

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]

Message-ID: <1466684699.8637.22.camel@redhat.com>
Date:	Thu, 23 Jun 2016 08:24:59 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Morten Rasmussen <morten.rasmussen@....com>
Cc:	peterz@...radead.org, mingo@...hat.com, dietmar.eggemann@....com,
	yuyang.du@...el.com, vincent.guittot@...aro.org,
	mgalbraith@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 02/13] sched/fair: Consistent use of prev_cpu in
 wakeup path

On Thu, 2016-06-23 at 10:56 +0100, Morten Rasmussen wrote:
> 
> I think that would lead to some minor changes in behaviour in a few
> corner cases, but I mainly wrote the patch as I thought it was very
> confusing that we could have different "prev_cpu"s in different parts
> of
> the select_task_rq_fair() code path.
> 
I agree that cleaning up the confusion is good.

-- 
All Rights Reversed.


Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)