[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mmap/munmap semantics

To: kernel@kvack.org
Subject: Re: mmap/munmap semantics
From: Richard Guenther <richard.guenther@student.uni-tuebingen.de>
Date: Thu, 24 Feb 2000 16:03:35 +0100 (MET)
cc: Richard Guenther <richard.guenther@student.uni-tuebingen.de>, "Stephen C. Tweedie" <sct@redhat.com>, Jamie Lokier <lk@tantalophile.demon.co.uk>, Linux Kernel List <linux-kernel@vger.rutgers.edu>, glame-devel@lists.sourceforge.net, Linux-MM <linux-mm@kvack.org>
In-Reply-To: <Pine.LNX.3.96.1000224100022.13614A-100000@kanga.kvack.org>
Sender: owner-linux-mm@kvack.org

On Thu, 24 Feb 2000 kernel@kvack.org wrote:

> On Thu, 24 Feb 2000, Richard Guenther wrote:
> 
> > Cool, too. So for now we will stay with zeroing by reading from /dev/zero
> > which does vm tricks in linux already.
> 
> It does not do tricks when you are dealing with a shared mapping.

Oops, so I misread the code in drivers/char/mem.c ... well, so how can I
get the same effect as for the private mapping? Not at the moment, I
think? So memset should be faster than reading from /dev/zero?

Richard.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

Follow-Ups:
- Re: mmap/munmap semantics
  - From: Jamie Lokier <lk@tantalophile.demon.co.uk>

References:
- Re: mmap/munmap semantics
  - From: <kernel@kvack.org>

Prev by Date: Re: mmap/munmap semantics
Next by Date: Re: mmap/munmap semantics
Prev by thread: Re: mmap/munmap semantics
Next by thread: Re: mmap/munmap semantics
Index(es):
- Date
- Thread