lkml.org 
[lkml]   [2002]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK
    On Wed, 18 Sep 2002, William Lee Irwin III wrote:
    >> The lockups I see range from hours to "it spun over the weekend, time to
    >> pull the plug".

    On Wed, Sep 18, 2002 at 07:36:00PM +0200, Ingo Molnar wrote:
    > this can happen if there's a genuine PID space squeeze wrt. nr_threads -
    > that is solved by adding Linus' suggestion to the PID allocator. I believe
    > you saw that problem, not any inherent get_pid() algorithmic inefficiency.
    > nevertheless we do lock up for 32 seconds if there are 32K PIDs allocated
    > in a row and last_pid hits that range - regardless of pid_max. (Depending
    > on the cache architecture it could take significantly more.)

    There were only 10K tasks, with likely consecutively-allocated PID's,
    and some minor background fork()/exit() activity, but there are more
    offenders on the read side than get_pid() itself.

    There is no question of PID space: the full 2^30 was configured in
    the tests done after the PID space expansion.


    Bill
    -
    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 13:17    [W:3.877 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site