Re: init's children list is long and slows reaping children.

 > no. Two _completely separate_ lists.
 > 
 > i.e. a to-be-reaped task will still be on the main list _too_. The main 
 > list is for all the PID semantics rules. The reap-list is just for 
 > wait4() processing. The two would be completely separate.

I guess this means we add another list head to struct task_struct.
Not that big a deal, but it does make me a little sad to think about
task_struct getting even bigger....

 - R.
-
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/

---

• Follow-Ups:
  • Re: init's children list is long and slows reaping children.
    • From: [email protected] (Eric W. Biederman)

• References:
  • Re: init's children list is long and slows reaping children.
    • From: Robin Holt <[email protected]>
  • Re: init's children list is long and slows reaping children.
    • From: [email protected] (Eric W. Biederman)
  • Re: init's children list is long and slows reaping children.
    • From: Oleg Nesterov <[email protected]>
  • Re: init's children list is long and slows reaping children.
    • From: Ingo Molnar <[email protected]>

• Prev by Date: coding style for long conditions (WAS: Re: [PATCH 25/90] ... blinky leds!!)
• Next by Date: Re: [PATCH 3/8] Use process freezer for cpu-hotplug
• Previous by thread: Re: init's children list is long and slows reaping children.
• Next by thread: Re: init's children list is long and slows reaping children.
• Index(es):
  • Date
  • Thread

[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]