linux-kernel - Re: [RFC][PATCH 3/4] sched: Change sched_class::set_cpus

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-next>] [day] [month] [year] [list]

Date:	Mon, 18 May 2015 10:32:16 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	pang.xunlei@....com.cn
Cc:	dedekind1@...il.com, juri.lelli@....com,
	linux-kernel@...r.kernel.org, linux-kernel-owner@...r.kernel.org,
	mgorman@...e.de, mingo@...nel.org, riel@...hat.com,
	rostedt@...dmis.org
Subject: Re: [RFC][PATCH 3/4] sched: Change sched_class::set_cpus_allowed
 calling context

On Mon, May 18, 2015 at 03:37:43PM +0800, pang.xunlei@....com.cn wrote:
> Hi Peter,
> 
> With this modification, I think the pushing action in my previous patch 
> "Check to push the task away after its affinity was changed" will not
> be able to be implemented inside sched_class::set_cpus_allowed().

Ah, right, I knew there was a patch I needed to look at.

I'll try and not forget, but there's a few regression reports I need to
look at first.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/