lkml.org 
[lkml]   [2004]   [Nov]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [Lse-tech] scalability of signal delivery for Posix Threads
    Date
    From
    So with CLONE_SIGHAND, we share the handler assignments and which signals
    are blocked, but retain the ability for individual threads to receive
    a signal. And when all of them receive signals in quick succession,
    we see lock contention because they're sharing the same (effectively)
    global lock to receive all of their (effectively) individual signals
    .. is that correct?

    Are you contending on tasklist_lock, or on siglock?

    It seems to me that scalability would be improved if we moved the
    siglock from the sighand structure to the task_struct.

    Only if you want to keep its current semantics of it being a lock for
    all things signal. Finer granularity would, it seems at first look,
    afford you the benefits you're looking for. (But not without the cost of
    a fair amount of work to make sure the new locks are utilized correctly.)
    For the problem you're describing, it sounds like the contention is occuring
    at delivery, so a new lock for pending, blocked, and real_blocked might be
    in order.

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

    \
     
     \ /
      Last update: 2005-03-22 14:08    [W:3.282 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site