Hi,
On Tue, 20 Nov 2001, Richard Gooch wrote:
> Delayed events are harmless, since devfs ensures correct ordering.
It's not about ordering, timing is currently unpredictable, anything
timing sensitive has to be very careful to touch anything in devfs.
> After consideration, I've decided to dynamically grow the event buffer
> as required, and free up space as it's not needed.
You should use a slab cache and acknowledge events as soon as they are
finished. Right now all processes are waiting until the devfsd is
completely finished and restarted at the same time. This is currently
limited by dropping events, with a dynamic event queue this can become a
problem.
> Since devfsd has to
> wait for a module load to complete, it's not a good idea to block
> waiting for free space in the event buffer (potential deadlock).
What do you mean?
bye, Roman
-
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 : Fri Nov 23 2001 - 21:00:27 EST