george anzinger wrote:
>
> Jim Houston wrote:
> I have also looked at the timer index stuff and made a few
> changes. If it get it working today, I will include it
> also. My changes mostly revolved around not caring about
> reusing a timer id. Would you care to comment on why you
> think reuse is bad?
>
> With out this feature the code is much simpler and does not
> keep around dead trees.
>
> -g
Hi George,
I assume the rationale is that not reusing the same id immediately helps
catch errors in user code. Since the id space is global, there
is more chance that one process may be manipulating another processes
timer. Reusing the same id makes this sort of problem harder to
catch.
The main reason I changed this in my patch is to avoid the CONFIG
limit on the number of timers. Since I don't have the fixed array,
I need a way to safely translate a user-space id into a kernel pointer.
Jim Houston Concurrent Computer Corp.
-
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/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:01:05 EST