Robin Holt <[email protected]> writes:
> I think this was originally coded with daemonize to avoid issues with
> reaping children. Dean Nelson can correct me if I am wrong. I assume
> this patch is going in as part of the set which will make these threads
> clear themselves from the children list and if that is the case, I can
> see no issues.
One of my earlier patches guarantees that kthreadd will have pid == 2.
daemonize actually explicitly reparents to init so using daemonize and
kernel_thread provides no help at all with respect to scaling. It in
fact guarantees you will be on init's list of child processes.
The work to enhance wait is a little tricky and it conflicts with the
utrace patches, which makes it hard to pursue at the moment.
I'm actually sorting out kthread stop so I can complete the pid namespace.
But since all kthreads are children of kthreadd this helps in a small
way with the scaling issue.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
