Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1179149 > unrolled thread

Re: [PATCH 2/3] kmod: Add up-to-date explanations on the purpose of each asynchronous levels

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH 2/3] kmod: Add up-to-date explanations on the purpose of  each asynchronous levels Andrew Morton <akpm@linux-foundation.org> - 2015-07-08 01:10 +0200
    Re: [PATCH 2/3] kmod: Add up-to-date explanations on the purpose of  each asynchronous levels Frederic Weisbecker <fweisbec@gmail.com> - 2015-07-08 15:00 +0200

#1179149 — Re: [PATCH 2/3] kmod: Add up-to-date explanations on the purpose of each asynchronous levels

On Mon,  6 Jul 2015 17:33:40 +0200 Frederic Weisbecker <fweisbec@gmail.com> wrote:

> There seem to be quite some confusions on the comments, likely due to
> changes that came after them.
> 
> Now since it's very non obvious why we have 3 levels of asynchronous
> code to implement usermodehelpers, it's important to comment in detail
> the reason of this layout.

There are still a few references to keventd in there.  One of them is
simply wrong: "runs as a child of keventd".  The userspace code is
actually a child of the khelper thread, yes?

I guess we should remove all kernel references to "keventd".  It got
renamed to "kworker".
--
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/

[toc] | [next] | [standalone]

#1179754

On Tue, Jul 07, 2015 at 04:07:58PM -0700, Andrew Morton wrote:
> On Mon,  6 Jul 2015 17:33:40 +0200 Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > There seem to be quite some confusions on the comments, likely due to
> > changes that came after them.
> > 
> > Now since it's very non obvious why we have 3 levels of asynchronous
> > code to implement usermodehelpers, it's important to comment in detail
> > the reason of this layout.
> 
> There are still a few references to keventd in there.  One of them is
> simply wrong: "runs as a child of keventd".  The userspace code is
> actually a child of the khelper thread, yes?
> 
> I guess we should remove all kernel references to "keventd".  It got
> renamed to "kworker".

Right, I think I missed them because I confused khelper with keventd.
In fact here they are all children of khelper, which is the singlethread
workqueue tied to kmod.

But I'm working on a new iteration that makes use of a global no numa
workqueue.
--
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/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web