[lkml]   [2002]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Analysis for Linux-2.5 fix/improve get_pid(), comparing various approaches
    On Friday 09 August 2002 12:05 pm, Linus Torvalds wrote:
    > On Fri, 9 Aug 2002, Hubertus Franke wrote:
    > > I dragged the various algorithms into a userlevel test program to figure
    > > out where the cut off points are with PID_MAX=32768. In this testprogram
    > > I maintain A tasks, and for 10 rounds (delete D random tasks and
    > > reallocate D tasks again) resulting in T=10*D total measured allocations.
    > Mind re-doing that with PID_MAX=999999 or similar? The whole point of the
    > current simple algorithm is that the common case (nay, done right, the
    > _only_ case) is where the number of threads << PID_MAX.

    Don't have time right now...
    Simply look at the numbers for the ratio you are expected.
    I would be very surprise if the relative curves would change
    when moving to 132K tasks and also populate the pid space only by
    let's say 25%.

    Otherwise, Paul can you run this....

    > That certainly used to be true with PID_MAX=32768 (not many people may
    > realize it, but in 1991 the maximum number of tasks in the system was
    > limited to 63, simply because of how the VM carved out the 4GB address
    > space).
    > Things have changed, but considering that some people think that 32k
    > threads are a limitation already, and that the current code should work
    > fine (and be pretty much optimal) with a larger PID_MAX, I really think
    > it's unfair to not even benchmark that case..
    > Linus

    -- Hubertus Franke (
    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: 2005-03-22 13:27    [W:0.023 / U:7.500 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site