On Thu, 2010-06-24 at 13:02 +1000, npiggin@xxxxxxx wrote: > > One difficulty with this approach is that a file can be removed from the list > by another CPU. We must track which per-cpu list the file is on. Scalability > could suffer if files are frequently removed from different cpu's list. Is this really a lot less complex than what I did with my fine-grained locked list? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
