From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 15 Mar 2007 13:54:32 +0100 From: Jens Axboe Subject: Re: [patch 1/2] splice: dont steal Message-ID: <20070315125432.GT15400@kernel.dk> References: <20070314121440.GA926@wotan.suse.de> <20070315115237.GM15400@kernel.dk> <20070315122207.GA8321@wotan.suse.de> <20070315122723.GQ15400@kernel.dk> <20070315124531.GD8321@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070315124531.GD8321@wotan.suse.de> Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: Andrew Morton , Linux Kernel Mailing List , Linux Memory Management List List-ID: On Thu, Mar 15 2007, Nick Piggin wrote: > On Thu, Mar 15, 2007 at 01:27:23PM +0100, Jens Axboe wrote: > > On Thu, Mar 15 2007, Nick Piggin wrote: > > > > > > We should be able to allow for it with the new a_ops API I'm working > > > on. > > > > "Should be" and in progress stuff, is it guarenteed to get there? > > Well considering that it is needed in order to solve 3 different deadlock > scenarios in the core write(2) path without taking a big performance hit, > I'd hope so ;) > > It isn't guaranteed, but I have only had positive feedback so far. Would > take a while to actually get merged, though. It's not that I don't believe you, I'm just a little reluctant to rip stuff out with a promise to fix it later when foo and bar are merged, since things like that have a tendency not to get done because they are forgotten :-) Do you have a test case for stealing failures? What I'm really asking is how critical is this? -- Jens Axboe -- 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: email@kvack.org