On Sun, Jan 28, 2007 at 04:48:06PM +0100, Ingo Molnar wrote: > i'm sorry, but do you realize that files_lock is a global lock, > triggered by /every single/ file close? Please check which thread you're in before you start such lengthy rants. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] mm: remove global locks from mm/highmem.c
- From: Ingo Molnar <[email protected]>
- Re: [PATCH] mm: remove global locks from mm/highmem.c
- References:
- [PATCH] mm: remove global locks from mm/highmem.c
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH] mm: remove global locks from mm/highmem.c
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] mm: remove global locks from mm/highmem.c
- From: Ingo Molnar <[email protected]>
- Re: [PATCH] mm: remove global locks from mm/highmem.c
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] mm: remove global locks from mm/highmem.c
- From: Ingo Molnar <[email protected]>
- [PATCH] mm: remove global locks from mm/highmem.c
- Prev by Date: [Fwd: [PATCH 2/7] lock_list: a fine grain locked double linked list]
- Next by Date: [-mm patch] fix GFS2 circular dependency
- Previous by thread: Re: [PATCH] mm: remove global locks from mm/highmem.c
- Next by thread: Re: [PATCH] mm: remove global locks from mm/highmem.c
- Index(es):
 |