[Cbe-oss-dev] [PATCH 3/3] spu sched: forced preemption at execution

Arnd Bergmann arnd at arndb.de
Tue Feb 27 23:30:23 EST 2007


On Tuesday 27 February 2007, Christoph Hellwig wrote:
> 
> > Hmm, the application should be able to change the priority and policy of a
> > ctx, if it
> > changes the priority of the controlling entity (ie. kernel thread or
> > process).  The
> > scheduling parameters should be able to be changed dynamically.
> 
> In Linux all scheduling information (priority, policy) is per-thread.
> That means the syscall to set it can't run concurrently to us beeing
> in this forced preemption code which is always run from the controlling
> thread in spu_run.  That beeing said we should update the scheduling
> information at ævery spu_run, which is a small change I've written
> up and that will be sent out soon.

Actually, I would prefer if we can manage to keep this information
out of the spufs data structures entirely. It probably means storing
a reference to the task_struct in the spu_context while we're inside
of spu_run(), but then we can always access the up-to-date priority
data from the right place.

	Arnd <><



More information about the cbe-oss-dev mailing list