From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Otte Subject: Re: [RFC/PATCH 2/4] fs/mm: execute in place (3rd version) Date: Thu, 26 May 2005 15:29:50 +0200 Message-ID: <4295CF4E.6010006@freenet.de> References: <1116866094.12153.12.camel@cotte.boeblingen.de.ibm.com> <1116869420.12153.32.camel@cotte.boeblingen.de.ibm.com> <20050524093029.GA4390@in.ibm.com> <42930B64.2060105@freenet.de> <20050524133211.GA4896@in.ibm.com> <42933B7A.3060206@freenet.de> <1117043475.26913.1540.camel@dyn318077bld.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: suparna@in.ibm.com, Linux Kernel Mailing List , linux-fsdevel , schwidefsky@de.ibm.com, Andrew Morton , Christoph Hellwig Return-path: To: Badari Pulavarty In-Reply-To: <1117043475.26913.1540.camel@dyn318077bld.beaverton.ibm.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Badari Pulavarty wrote: > This way I was able to reduce 129 lines of your code. > >This patch is on top of your current set and I haven't even >tried compiling it. Needs cleanup. > > > Going to try it out, looks like a reasonable way to go afaics. Also, our gcc developer Ulrich Weigand found a way that might get us rid of the duplication: We can just implement sync read/write and rely on fallbacks or do simple wrappers where that doesn't work out well. Should not show much penalty since we do sync IO immedieately (memcpy) anyway. Suparna is right: there needs to be a 3rd way