[lkml]   [2006]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [Patch][RFC] Disabling per-tgid stats on task exit in taskstats
    Andrew Morton wrote:
    >Jay Lan <> wrote:
    >>If you can show me how to not sending per-tgid with current patchset,
    >>i would be very happy to drop this request.
    >pleeeze, not a global sysctl. It should be some per-client subscription thing.

    Per-client subscription is not possible since it is the push (multicast)
    model we
    talk about and delayacct needs tgid.

    >But the overhead at present is awfully low. If we don't need this ability
    >at present (and I don't think we do) then a paper design would be
    >sufficient at this time. As long as we know we can do this in the future
    >without breaking existing APIs then OK.
    i can see if an exiting process is the only process in the thread group,
    the (not is_thread_group) condition would be true. So, that leaves
    multi-threaded applications that are not interested in tgid-data still
    receive 2x taskstats data.

    Is a system-wide switch that bad? A site that needs tgid stats can live
    with the performance consequence while those do not need tgid can
    enjoy a pure per-task stats data. (I would argue that a thread group
    is some sort of task aggregate.)

    How about sending tgid stats when the last process in the group exist?
    But do not send it if not the last in the thread?

    - jay

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-06-10 01:49    [W:0.020 / U:1.300 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site