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

Ravikiran G Thirumalai wrote:
> 
> On Tue, Jan 17, 2006 at 10:59:02PM +0300, Oleg Nesterov wrote:
> >
> > But don't we already discussed this issue? I think that RUSAGE_SELF
> > case always not 100% accurate, so it is Ok to ignore this race.
> 
> Take the case when an exiting thread has a large utime stime value, and
> rusage reports utime before thread exit and stime after thread exit... the
> result would look wierd.
> So IMHO, while inaccuracies in task_struct->xxx time can be tolerated, it
> might not be such a good idea to for task_struct->signal->xxx counters.

Yes, you are right. Now I don't understand why I didn't understand this
before. Thank you, Ravikiran.

Oleg.
-
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:
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Ravikiran G Thirumalai <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Oleg Nesterov <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Ravikiran G Thirumalai <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Oleg Nesterov <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Ravikiran G Thirumalai <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Oleg Nesterov <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Ravikiran G Thirumalai <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Oleg Nesterov <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Ravikiran G Thirumalai <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Oleg Nesterov <[email protected]>
  • Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
    • From: Ravikiran G Thirumalai <[email protected]>

• Prev by Date: hugetlb bug
• Next by Date: [PATCH] e1000 C style badness
• Previous by thread: Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
• Next by thread: Re: ATA Write Error and Time-out Notification in User Space
• 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]