Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 27 Jul 2002 12:22:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 27 Jul 2002 12:22:00 -0400 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237]:8446 "EHLO passion.cambridge.redhat.com") by vger.kernel.org with ESMTP id ; Sat, 27 Jul 2002 12:21:59 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 From: David Woodhouse X-Accept-Language: en_GB In-Reply-To: <1027712005.14773.12.camel@irongate.swansea.linux.org.uk> References: <1027712005.14773.12.camel@irongate.swansea.linux.org.uk> <3D418DFD.8000007@deming-os.org> To: Alan Cox Cc: Russell Lewis , linux-kernel@vger.kernel.org Subject: Re: Looking for links: Why Linux Doesn't Page Kernel Memory? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Jul 2002 17:24:58 +0100 Message-ID: <16918.1027787098@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1095 Lines: 27 alan@lxorguk.ukuu.org.uk said: > Memory is relatively cheap, and the complexity of such a paging > kernel is huge (you have to pin down disk driver and I/O paths for > example). Linux prefers to try to keep simple debuggable approaches to > things. You could do it. Start with kmalloc_pageable (probably actually vmalloc_pageable) and introduce new sections for pageable data and text, which can be marked just as init sections are currently. Introduce it slowly, adding it a little at a time like we did SMP, and like we _should_ have done preemption. It's debatable what kind of benefit it would give you over and above just fixing specific cases like page tables, though. Most of the systems where I've _really_ cared about RAM to that extent have been systems without any local storage which could sanely be used for swap. -- dwmw2 - 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/