Re: get_pid() : enahancement

> I was just wondering on the efficiency of get_pid() implemetation... Although > 'next_safe' concept in this function seems useful but I think we now need a > robust PID allocator.. get_pid() isnt showing up on kernel profile runs I've seen, and that doesn't actually suprise me. Its not a

get_pid() : enahancement

In 2.4 kernel we now have no limit on the number of tasks running on a system (no NR_TASKS anymore)... I was just wondering on the efficiency of get_pid() implemetation... Although 'next_safe' concept in this function seems useful but I think we now need a robust PID allocator.. We can have a

get_pid() : enahancement

In 2.4 kernel we now have no limit on the number of tasks running on a system (no NR_TASKS anymore)... I was just wondering on the efficiency of get_pid() implemetation... Although 'next_safe' concept in this function seems useful but I think we now need a robust PID allocator.. We can have a

Re: get_pid() : enahancement

I was just wondering on the efficiency of get_pid() implemetation... Although 'next_safe' concept in this function seems useful but I think we now need a robust PID allocator.. get_pid() isnt showing up on kernel profile runs I've seen, and that doesn't actually suprise me. Its not a normal