linux-kernel - Re: [RFC -v2 PATCH 2/3] sched: add yield

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:	Tue, 14 Dec 2010 15:54:09 +0530
From:	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
To:	Mike Galbraith <efault@....de>
Cc:	Rik van Riel <riel@...hat.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, Avi Kiviti <avi@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [RFC -v2 PATCH 2/3] sched: add yield_to function

On Tue, Dec 14, 2010 at 07:08:16AM +0100, Mike Galbraith wrote:
> > +/*
> > + * Yield the CPU, giving the remainder of our time slice to task p.
> > + * Typically used to hand CPU time to another thread inside the same
> > + * process, eg. when p holds a resource other threads are waiting for.
> > + * Giving priority to p may help get that resource released sooner.
> > + */
> > +void yield_to(struct task_struct *p)
> > +{
> > +	unsigned long flags;
> > +	struct rq *rq, *p_rq;
> > +
> > +	local_irq_save(flags);
> > +	rq = this_rq();
> > +again:
> > +	p_rq = task_rq(p);
> > +	double_rq_lock(rq, p_rq);
> > +	if (p_rq != task_rq(p)) {
> > +		double_rq_unlock(rq, p_rq);
> > +		goto again;
> > +	}
> > +
> > +	/* We can't yield to a process that doesn't want to run. */
> > +	if (!p->se.on_rq)
> > +		goto out;
> > +
> > +	/*
> > +	 * We can only yield to a runnable task, in the same schedule class
> > +	 * as the current task, if the schedule class implements yield_to_task.
> > +	 */
> > +	if (!task_running(rq, p) && current->sched_class == p->sched_class &&
> > +			current->sched_class->yield_to)
> > +		current->sched_class->yield_to(rq, p);
> > +
> > +out:
> > +	double_rq_unlock(rq, p_rq);
> > +	local_irq_restore(flags);
> > +	yield();
> > +}
> > +EXPORT_SYMBOL_GPL(yield_to);
> 
> That part looks ok, except for the yield cross cpu bit.  Trying to yield
> a resource you don't have doesn't make much sense to me.

So another (crazy) idea is to move the "yieldee" task on another cpu over to 
yielding task's cpu, let it run till the end of yielding tasks slice and then
let it go back to the original cpu at the same vruntime position!

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