Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 25 Jul 2001 12:12:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 25 Jul 2001 12:11:59 -0400 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:61487 "EHLO flinx.biederman.org") by vger.kernel.org with ESMTP id ; Wed, 25 Jul 2001 12:11:47 -0400 To: Daniel Phillips Cc: landley@webofficenow.com, Marcelo Tosatti , Rik van Riel , linux-kernel@vger.kernel.org, Ben LaHaise , Mike Galbraith Subject: Re: [RFC] Optimization for use-once pages In-Reply-To: <01072415352102.00631@localhost.localdomain> <01072514530401.00907@starship> From: ebiederm@xmission.com (Eric W. Biederman) Date: 25 Jul 2001 10:05:47 -0600 In-Reply-To: <01072514530401.00907@starship> Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.5 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 Original-Recipient: rfc822;linux-kernel-outgoing Daniel Phillips writes: > On Wednesday 25 July 2001 10:32, Eric W. Biederman wrote: > > Consider having a swapfile on tmpfs. > > Ooh, a truly twisted thought. > > We'd know we're making progress when we can prove it doesn't deadlock. Given all of that I think I going to go try to hack up a version that works. The ensuring we don't deadlock sounds like it will require some shared mechanisms with journaling filesystems. The whole pinned ram problem. So to some extent it looks like a 2.4 problem. Though I'd rather solve it in 2.5.x first. Eric - 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/