On Wed, 25 Jun 2003, Kedar Sovani wrote: > if the problem is only with the holding of data, you could keep a ref count > for the data, and delete it only when it zeroes out. > > But then the checking for callback existence and calling the callback should > be done atomically. You could of course just use a semaphore if you want to be able to sleep. For ensuring data is still available before deleting the callback and it's associated data, you could register an RCU (Read Copy Update) callback. Zwane -- function.linuxpower.ca -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
