linux-kernel - Re: [PATCH v3 1/4] sched/rt: Check to push the task away after its affinity was changed

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

Message-ID: <20150530123049.21ed5168@gandalf.local.home>
Date:	Sat, 30 May 2015 12:30:49 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	pang.xunlei@....com.cn, Juri Lelli <juri.lelli@...il.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
	Xunlei Pang <pang.xunlei@...aro.org>,
	Xunlei Pang <xlpang@....com>
Subject: Re: [PATCH v3 1/4] sched/rt: Check to push the task away after its
 affinity was changed

On Sat, 30 May 2015 12:54:23 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> On Sat, 2015-05-30 at 10:20 +0200, Peter Zijlstra wrote:
> > Makes me like the thing even less though..
> 
> Steven, why do we normally push on schedule()? Would not the natural
> location be where we add to pushable_tasks?
> 
> Which would be here in set_cpus_allowed() and wakeups. schedule() seems
> like a second best location.

What about when an RT task gets preempted by a higher prio task. We may
need to push the preempted one. You can't do that at wakeup.

-- Steve


--
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/