Messages in this thread | | | Date | Wed, 18 Jan 2006 12:17:52 +0300 | From | Oleg Nesterov <> | Subject | 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |