Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751265AbWE3FHw (ORCPT ); Tue, 30 May 2006 01:07:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751274AbWE3FHw (ORCPT ); Tue, 30 May 2006 01:07:52 -0400 Received: from smtp102.mail.mud.yahoo.com ([209.191.85.212]:52563 "HELO smtp102.mail.mud.yahoo.com") by vger.kernel.org with SMTP id S1751271AbWE3FHv (ORCPT ); Tue, 30 May 2006 01:07:51 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=v7n5RazhkuUx7v7vZuTH5Y81IvrzUC+4D6vwm+WFvaj2s0GtlEikjl+XpB+v/0jsMMMEXFgnoBWknqsg2YlEtzpUHpCL9XBIDxLRmZbK1GQGG77RseSSHj6FrjtBX99LaNBh++XHhn7x+jKULo4SQLIov2GQrOVBGcDLeMpgo6s= ; Message-ID: <447BD31E.7000503@yahoo.com.au> Date: Tue, 30 May 2006 15:07:42 +1000 From: Nick Piggin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051007 Debian/1.7.12-1 X-Accept-Language: en MIME-Version: 1.0 To: Linus Torvalds CC: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, mason@suse.com, andrea@suse.de, hugh@veritas.com, axboe@suse.de Subject: Re: [rfc][patch] remove racy sync_page? References: <447AC011.8050708@yahoo.com.au> <20060529121556.349863b8.akpm@osdl.org> <447B8CE6.5000208@yahoo.com.au> <20060529183201.0e8173bc.akpm@osdl.org> <447BB3FD.1070707@yahoo.com.au> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2000 Lines: 56 Linus Torvalds wrote: > > On Tue, 30 May 2006, Nick Piggin wrote: > >>I guess so. Is plugging still needed now that the IO layer should >>get larger requests? > > > Why do you think the IO layer should get larger requests? For workloads where plugging helps (ie. lots of smaller, contiguous requests going into the IO layer), should be pretty good these days due to multiple readahead and writeback. > > I really don't understand why people dislike plugging. It's obviously > superior to non-plugged variants, exactly because it starts the IO only > when _needed_, not at some random "IO request feeding point" boundary. If you submit IO, it will be needed at some point in time. The benefit of plugging is to hold it there in anticipation of more IO to merge with this request. Not sure what you mean by IO request feeding point...? > > In other words, plugging works _correctly_ regardless of any random > up-stream patterns. That's the kind of algorithms we want, we do NOT want > to have the IO layer depend on upstream always doing the "Right > Thing(tm)". It is a heuristic. I don't see anything obviously correct or incorrect about it. If you were to submit some asynch requests and _knew_ that no other requests would be merged with them, plugging would be the wrong thing to do because the disks would be needlessly idle. > > So exactly why would you want to remove it? Because of this bug ;) I'm not saying it would never be of any benefit; I was hoping that it might be unneeded and getting rid of it would fix this bug and simplify a lot too. Anyway, clearly a plug friendly bugfix needs to be implemented regardless. -- SUSE Labs, Novell Inc. Send instant messages to your online friends http://au.messenger.yahoo.com - 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/