lkml.org 
[lkml]   [2014]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kGraft to -next [was: 00/21 kGraft]
On Sat, 5 Jul 2014, Jiri Kosina wrote:

> > > The same holds for the kernel threads -- until all (or most of) the
> > > kthreads are converted to workqueues, the obivous choice, that should
> > > cover most of the use-cases, has been made.
> >
> > But, this is different.
>
> Quite frankly, I have to say that I don't personally see *that* big
> difference. In both cases we are making assumptions about semantics, and
> are trying to get "as close as possible" to the point in time where the
> set of assumptions can be made as minimal as possible.
>
> With userspace thread, this is kernel/userspace boundary. With kthread,
> this is starting of new iteration of the main loop / try_to_freeze().
>
> We were not able to come up with anything better. Alan, you were
> stating "I don't see why it can't use the kernel freeze functionality?".
> What exactly was your suggestion, if not this, please?

Seems like there was no further activity on this wile I was on vacation,
so let me resurrect this.

Alan, either we are already doing what you suggested, or I misunderstood
your proposal above. Could you please elaborate?

Thanks,

--
Jiri Kosina
SUSE Labs


\
 
 \ /
  Last update: 2014-07-29 16:41    [W:0.061 / U:1.460 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site