lkml.org 
[lkml]   [2007]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] RT: Add priority-queuing and priority-inheritance to workqueue infrastructure
On 08/01, Daniel Walker wrote:
>
> On Wed, 2007-08-01 at 19:01 +0200, Peter Zijlstra wrote:
> > > static void insert_work(struct cpu_workqueue_struct *cwq,
> > > struct work_struct *work, int tail)
> > > {
> > > + int prio = current->normal_prio;
> > > +
> > > set_wq_data(work, cwq);
> > > /*
> > > * Ensure that we get the right work->data if we see the
> > > * result of list_add() below, see try_to_grab_pending().
> > > */
> > > smp_wmb();
> > > - if (tail)
> > > - list_add_tail(&work->entry, &cwq->worklist);
> > > - else
> > > - list_add(&work->entry, &cwq->worklist);
> > > + plist_node_init(&work->entry, prio);
> > > + plist_add(&work->entry, &cwq->worklist);
> >
> > perhaps we ought to handle tail, perhaps not, not sure what the
> > consequences are.
>
> The plist doesn't distinguish since it's a sorted list. There is no way
> to force something to the back of the list ..
>
> It seems like the "tail" option was the old way to prioritize.. I think
> It could be removed since we're always priority ordering now anyway..

No, the "tail" option has nothing to do with prioritize, we can't remove
it. Please look at the code.

Also, flush_workqueue() must not be delayed by the new incoming work_struct's,
the change like this breaks this assumption.

Oleg.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-08-01 20:29    [W:0.061 / U:26.544 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site