| Date | Tue, 4 Jun 2013 10:53:22 -0400 | From | "J. Bruce Fields" <> | Subject | Re: [PATCH v1 11/11] locks: give the blocked_hash its own spinlock |
| |
On Tue, Jun 04, 2013 at 07:46:40AM -0700, Christoph Hellwig wrote: > Having RCU for modification mostly workloads never is a good idea, so > I don't think it makes sense to mention it here. > > If you care about the overhead it's worth trying to use per-cpu lists, > though.
Yes. The lock and unlock could happen on different CPU's--but I think you can make the rule that the lock stays associated with the list it was first put on, and then it's correct in general and hopefully quick in the common case.
--b.
|