Messages in this thread | | | Date | Fri, 24 Feb 2006 15:21:41 -0500 (EST) | From | Alan Stern <> | Subject | Re: [PATCH] Avoid calling down_read and down_write during startup |
| |
On Fri, 24 Feb 2006, Benjamin LaHaise wrote:
> > > A read lock is a memory barrier. That's why I'm opposed to using non-rcu > > > style locking for them. > > > > But RCU-style locking can't be used in situations where the reader may > > block. So it's not possible to use it with blocking notifier chains. > > Then we shouldn't have non-atomic notifier chains in performance critical > codepaths. The original implementation's hooks into critical paths held > these characteristics. If that property has been broken, please fix it > instead of adding more locking.
Sorry, no can do. You'll have to complain to the people who put blocking code into critical paths in the first place. I don't know which paths are critical nor do I know how to change the code to make it non-blocking.
Or you could write some patches yourself instead of asking other people to do it for you.
Alan Stern
- 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/
| |