From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753809AbYDGFpw (ORCPT ); Mon, 7 Apr 2008 01:45:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751216AbYDGFpo (ORCPT ); Mon, 7 Apr 2008 01:45:44 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:34200 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751088AbYDGFpo (ORCPT ); Mon, 7 Apr 2008 01:45:44 -0400 Date: Sun, 6 Apr 2008 22:45:41 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andrea Arcangeli cc: Hugh Dickins , Robin Holt , Avi Kivity , Izik Eidus , kvm-devel@lists.sourceforge.net, Peter Zijlstra , general@lists.openfabrics.org, Steve Wise , Roland Dreier , Kanoj Sarcar , steiner@sgi.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com, Nick Piggin Subject: Re: [PATCH] mmu notifier #v11 In-Reply-To: <20080405002330.GF14784@duo.random> Message-ID: References: <20080402220148.GV19189@duo.random> <20080402221716.GY19189@duo.random> <20080403151908.GB9603@duo.random> <20080404202055.GA14784@duo.random> <20080405002330.GF14784@duo.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 5 Apr 2008, Andrea Arcangeli wrote: > In short when working with single pages it's a waste to block the > secondary-mmu page fault, because it's zero cost to invalidate_page > before put_page. Not even GRU need to do that. That depends on what the notifier is being used for. Some serialization with the external mappings has to be done anyways. And its cleaner to have one API that does a lock/unlock scheme. Atomic operations can easily lead to races.