On Sat, Sep 21, 2002 at 04:15:10PM +0200, Manfred Spraul wrote:
> One solution would be to replace the idtag hash with an idtag tree.
> Then get_pid_list() could return an array of sorted pids, and finding
> the next pid after unlocking the task_lock would be just a tree lookup
> (find first pid larger than x).
> And a sorted tree would make it possible find the next safe range for
> get_pid() with O(N) instead of O(N^2).
There are incremental / O(1) methods for filling the directory as well.
Also, a tree does not preclude additional hashing. Personally, I'd
consider O(N) catastrophic as well, especially when done on multiple
cpus simultaneously. In fact, a large chunk of this is obtaining hard
bounds on the hold time of the tasklist_lock so writers have a remote
chance of getting into critical sections.
Another very important aspect of it is that the tasklist cachelines
aren't incessantly pounded, which is important even for UP.
At any rate, if you care to send something to me I will doublecheck
whether it NMI oopses on my machines.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/