From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933566AbXDDPsv (ORCPT ); Wed, 4 Apr 2007 11:48:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934038AbXDDPsv (ORCPT ); Wed, 4 Apr 2007 11:48:51 -0400 Received: from ns.suse.de ([195.135.220.2]:58995 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933566AbXDDPsu (ORCPT ); Wed, 4 Apr 2007 11:48:50 -0400 Date: Wed, 4 Apr 2007 17:48:39 +0200 From: Andrea Arcangeli To: Linus Torvalds Cc: Nick Piggin , Hugh Dickins , Andrew Morton , Linux Memory Management List , tee@sgi.com, holt@sgi.com, Linux Kernel Mailing List Subject: Re: [rfc] no ZERO_PAGE? Message-ID: <20070404154839.GI19587@v2.random> References: <20070329075805.GA6852@wotan.suse.de> <20070330024048.GG19407@wotan.suse.de> <20070404033726.GE18507@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 04, 2007 at 08:35:30AM -0700, Linus Torvalds wrote: > Anyway, I'm not against this, but I can see somebody actually *wanting* > the ZERO page in some cases. I've used the fact for TLB testing, for > example, by just doing a big malloc(), and knowing that the kernel will > re-use the ZERO_PAGE so that I don't get any cache effects (well, at least > not any *physical* cache effects. Virtually indexed cached will still show > effects of it, of course, but I haven't cared). Ok, those cases wanting the same zero page, could be fairly easily converted to an mmap over /dev/zero (without having to run 4k large mmap syscalls or nonlinear).