From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760215AbXERVEe (ORCPT ); Fri, 18 May 2007 17:04:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754375AbXERVE2 (ORCPT ); Fri, 18 May 2007 17:04:28 -0400 Received: from netops-testserver-4-out.sgi.com ([192.48.171.29]:40175 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753152AbXERVE1 (ORCPT ); Fri, 18 May 2007 17:04:27 -0400 Date: Fri, 18 May 2007 14:04:27 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Jan Engelhardt cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, dgc@sgi.com, Hugh Dickins Subject: Re: [patch 08/10] shmem: inode defragmentation support In-Reply-To: Message-ID: References: <20070518181040.465335396@sgi.com> <20070518181120.477184338@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 18 May 2007, Jan Engelhardt wrote: > Do we need *this*? (compare procfs) > > I believe that shmfs's inodes remain "more" in memory than those of > procfs. That is, procfs ones can find their way out (we can regenerate > it), while shmfs/tmpfs/ramfs/etc. should not do that (we'd lose the > file). Ahh... Okay so shmem inodes are not defraggable.