From mboxrd@z Thu Jan 1 00:00:00 1970 From: Coywolf Qi Hunt Subject: Re: [RFC/PATCH 0/5] add execute in place support Date: Wed, 1 Jun 2005 18:12:55 +0800 Message-ID: <2cd57c9005060103122b2bae36@mail.gmail.com> References: <428216DF.8070205@de.ibm.com> Reply-To: coywolf@lovecn.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, schwidefsky@de.ibm.com, akpm@osdl.org Return-path: Received: from nproxy.gmail.com ([64.233.182.198]:49122 "EHLO nproxy.gmail.com") by vger.kernel.org with ESMTP id S261176AbVFAKM4 convert rfc822-to-8bit (ORCPT ); Wed, 1 Jun 2005 06:12:56 -0400 Received: by nproxy.gmail.com with SMTP id o25so39483nfa for ; Wed, 01 Jun 2005 03:12:55 -0700 (PDT) To: cotte@freenet.de In-Reply-To: <428216DF.8070205@de.ibm.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 5/11/05, Carsten Otte wrote: > Folks, > > this is the intro to a small series of patches that introduce execute > in place into the I/O stack. File I/O to memory-backed block > devices is performed directly, bypassing the page cache and io > schedulers. On s390, we use this for block devices based on shared > memory between multiple virtual machines. This is also useful on > embedded systems where the block device is located on a flash chip. > This work is a result of a prior discussion with Andrew Morton > about my first implementation which basically was a filesystem > derived from ext2. > > As I'd like to aim for integration into -mm and vanilla later on, > I'd like to encourage everyone to give it a read and provide > feedback. All patches apply against git-head as of today. I feel the name "execute in place" misleading. This is not the real XIP, IMHO. Invent another term or be tolerant? -- Coywolf Qi Hunt http://ahbl.org/~coywolf/