Re: [rfc][patch] Avoid taking global tasklist_lock for single threaded process at getrusage()

On Sat, 24 Dec 2005, Oleg Nesterov wrote:

> I can't understand this. 'p' can do clone(CLONE_THREAD) immediately
> after 'if (!thread_group_empty(p))' check.

Only if p != current. As discussed later the lockless approach is 
intened to only be used if p == current.
-
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: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Oleg Nesterov <[email protected]>

• References:
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threaded process at getrusage()
    • From: Oleg Nesterov <[email protected]>

• Prev by Date: Re: [PATCH] SPI: add support for PNX/SPI controller
• Next by Date: Re: Linux 2.6.14.5
• Previous by thread: Re: [rfc][patch] Avoid taking global tasklist_lock for single threaded process at getrusage()
• Next by thread: Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
• 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]