Re: [Patch][RFC] Disabling per-tgid stats on task exit in taskstats

[Shailabh Nagar <nagar@watson.ibm.com>]

Paul Jackson wrote:

> Shailabh wrote:
>  
>
> > Nope...as long as there are users who are using cpusets ONLY as a means 
> > of reducing sockets to listen to, timestamps will be needed.
> >    
>
> Could you take one more stab at explaining this.
>
> It made no sense to me this time around.  Sorry.
>
>  

In the current taskstats interface, there is only a single stream of 
taskstats structures coming out
from the kernel. There is some ordering there. Lets say this ordering 
info is of some relevance to a
consumer of taskstats (very big and possibly faulty assumption there !)

Now we move to a design where the kernel is sending the same data out in 
multiple streams.
If the consumer wants to reconstruct the ordering she would have got 
under the current scheme (even
approximately),  she would need to know how to merge sort these streams 
and for that she would
need timestamp data on each of the taskstats structs.

Assumption is a bit of a stretch admittedly. But since timestamping 
costs so little, might as well put one
in (will also help CSA do one less thing)

--Shailabh


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