Re: Per container statistics (containerstats)

On 6/7/07, Balbir Singh <[email protected]> wrote:

> this needs tasklist_lock?
>

rcu_read_lock() should be fine. From Eric's patch at

2.6.17-mm2 - proc-remove-tasklist_lock-from-proc_pid_readdir.patch

The patch mentions that "We don't need the tasklist_lock to safely
iterate through processes anymore."

Containers V10 includes an iterator interface for listing the member
tasks of a container, which avoids scanning the entire tasklist.
Downside is that it currently requires taking a read_lock on a global
lock, but I hope to improve on that in the future.

Paul
-
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/

---

• References:
  • Per container statistics (containerstats)
    • From: Balbir Singh <[email protected]>
  • Re: Per container statistics (containerstats)
    • From: Andrew Morton <[email protected]>
  • Re: Per container statistics (containerstats)
    • From: Balbir Singh <[email protected]>

• Prev by Date: Re: [PATCH] enable interrupts in user path of page fault.
• Next by Date: Re: [PATCH] enable interrupts in user path of page fault.
• Previous by thread: Re: Per container statistics (containerstats)
• Next by thread: Re: Per container statistics (containerstats)
• 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]