> > > On Mon, 15 Jan 2007, YAMAMOTO Takashi wrote:
> > > > > On Sat, 13 Jan 2007, Iain Hibbert wrote:
> > > > > > On Sat, 13 Jan 2007, YAMAMOTO Takashi wrote:
> > > > > > > once callout_setwork() is called on a callout,
> > > > > > > callout_schedule() is only legal operation on the callout.
> > > > > >
> > > > > > callout_schedule() cannot be called multiple times, either..
> > > > >
> > > > > I think that these issues would go away, if callout managed its own
> > > > > kthread, instead of utilising workqueue to do that?
> 
> I think the attached method is cleaner (is untried, not sure if its
> complete or the locking is ok?)

i have no objections against the method.
please complete it and commit. :)

if you mean to support all callout(9) functionalities unlike mine,
"c->c_flags = (c->c_flags & ~CALLOUT_PENDING) |
(CALLOUT_FIRED|CALLOUT_INVOKING);" should be done by the thread
in the case of CALLOUT_THREAD.

YAMAMOTO Takashi