Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932218AbVLHT0Z (ORCPT ); Thu, 8 Dec 2005 14:26:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932226AbVLHT0Z (ORCPT ); Thu, 8 Dec 2005 14:26:25 -0500 Received: from [194.90.237.34] ([194.90.237.34]:20533 "EHLO mtlex01.yok.mtl.com") by vger.kernel.org with ESMTP id S932218AbVLHT0Y (ORCPT ); Thu, 8 Dec 2005 14:26:24 -0500 Date: Thu, 8 Dec 2005 21:29:18 +0200 From: "Michael S. Tsirkin" To: Hugh Dickins Cc: Gleb Natapov , Benjamin Herrenschmidt , Petr Vandrovec , Nick Piggin , Badari Pulavarty , Linux Kernel Mailing List Subject: Re: set_page_dirty vs set_page_dirty_lock Message-ID: <20051208192918.GC13886@mellanox.co.il> Reply-To: "Michael S. Tsirkin" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 443 Lines: 13 Quoting Hugh Dickins : > Many would be pleased if we could manage without set_page_dirty_lock. Yes, it forces me to bounce a work into a queue from the interrupt. Thanks! -- MST - 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/