![]() | |||||||||||||
Messages in this thread |
Nick Piggin <nickpiggin@yahoo.com.au> wrote: > > (I guess reclaim might be one, but quite rare -- any other significant > lock_page users that we might hit?) The only time 2.6 holds lock_page() for a significant duration is when bringing the page uptodate with readpage or memset. The scalability risk here is 100 CPUs all faulting in the same file in the same pattern. Like the workload which caused the page_table_lock splitup (that was with anon pages). All the CPUs could pretty easily get into sync and start arguing over every single page's lock. - 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/ | ||||||||||||
| Last update: 2006-01-13 08:50 [from the cache] ©2003-2008 | |||||||||||||