Messages in this thread | | | Subject | Re: [PATCH 3/3] fs: rcu protect inode hash lookups | From | Eric Dumazet <> | Date | Mon, 01 Nov 2010 16:29:22 +0100 |
| |
Le mardi 02 novembre 2010 à 00:44 +1100, Dave Chinner a écrit :
> Perhaps you should rename that file "slab_destroy_by_rcu-tips.txt", > because the current name seems unrelated to the contents. :/ >
Hmm, I dont know, this doc really is about the nulls thing.
This stuff also addressed one problem I forgot to tell you about: During a lookup, you might find an item that is moved to another chain by another cpu, so your lookup is redirected to another chain. You can miss your target.
You must find a way to detect such thing to restart the lookup at the beginning (of the right chain).
Either you stick the chain number in a new inode field (that costs extra memory), or you use the 'nulls' value that can let you know if you ended your lookup in the right chain.
-- 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/
| |