lkml.org 
[lkml]   [2004]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Suspend2 merge preparation: Rationale behind the freezer changes.
Date
Am Freitag, 21. Mai 2004 19:15 schrieb Pavel Machek:
> Hi!
>
> > > > > > Kernel threads are different, and each must be handled separately,
> > > > > > maybe even with some ordering. But there's relatively small number of
> > > > > > kernel threads...
> > > > >
> > > > > Yes, but what order? I played with that problem for ages. Perhaps I just
> > > > >   didn't find the right combination.
> > > >
> > > > How about recording the order of creation and do it in opposite order?
> > >
> > > Order of creation is pretty much hidden in pid, but I do not think
> > > that will work.
> >
> > Why? Build a list during kernel thread creation. It is not a hot code path.
>
> Maybe the order in which kernel threads were created is not the same
> as the order how they need to be frozen?

Possible, but unlikely. If there can be a deadlock if they are frozen in
reverse order, the same problem existed during creation and needed
to be specially handled.

Regards
Oliver
-
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: 2005-03-22 14:03    [W:0.061 / U:0.540 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site