Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 3 Aug 2002 00:22:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 3 Aug 2002 00:22:14 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:18442 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Sat, 3 Aug 2002 00:22:14 -0400 Date: Fri, 2 Aug 2002 21:26:52 -0700 (PDT) From: Linus Torvalds To: davidm@hpl.hp.com cc: Gerrit Huizenga , Hubertus Franke , , , Kernel Mailing List Subject: Re: large page patch (fwd) (fwd) In-Reply-To: <15691.22889.22452.194180@napali.hpl.hp.com> Message-ID: 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 Content-Length: 1121 Lines: 30 On Fri, 2 Aug 2002, David Mosberger wrote: > > My terminology is perhaps a bit too subtle: I user "superpage" > exclusively for the case where multiple pages get coalesced into a > larger page. The "large page" ("huge page") case that you were > talking about is different, since pages never get demoted or promoted. Ahh, ok. > I wasn't disagreeing with your case for separate large page syscalls. > Those syscalls certainly simplify implementation and, as you point > out, it well may be the case that a transparent superpage scheme never > will be able to replace the former. Somebody already had patches for the transparent superpage thing for alpha, which supports it. I remember seeing numbers implying that helped noticeably. But yes, that definitely doesn't work for humongous pages (or whatever we should call the multi-megabyte-special-case-thing ;). Linus - 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/