From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <41B92C11.80106@yahoo.com.au> Date: Fri, 10 Dec 2004 15:54:41 +1100 From: Nick Piggin MIME-Version: 1.0 Subject: Re: page fault scalability patch V12 [0/7]: Overview and performance tests References: <41B92567.8070809@yahoo.com.au> In-Reply-To: <41B92567.8070809@yahoo.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: Hugh Dickins , Christoph Lameter , Linus Torvalds , Andrew Morton , Benjamin Herrenschmidt , linux-mm@kvack.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org List-ID: Nick Piggin wrote: > Yep, the update_mmu_cache issue is real. There is a parallel problem > that is update_mmu_cache can be called on a pte who's page has since > been evicted and reused. Again, that looks safe on IA64, but maybe > not on other architectures. > > It can be solved by moving lru_cache_add to after update_mmu_cache in > all cases but the "update accessed bit" type fault. I solved that by > simply defining that out for architectures that don't need it - a raced > fault will simply get repeated if need be. > The page-freed-before-update_mmu_cache issue can be solved in that way, not the set_pte and update_mmu_cache not performed under the same ptl section issue that you raised. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org