| Subject | Re: [patch 06/52] fs: scale files_lock | From | Peter Zijlstra <> | Date | Thu, 24 Jun 2010 09:52:17 +0200 |
| |
On Thu, 2010-06-24 at 13:02 +1000, npiggin@suse.de 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?
|