[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proxy memory objects patch
From: |
Marcus Brinkmann |
Subject: |
Re: proxy memory objects patch |
Date: |
Wed, 4 Dec 2002 16:20:04 +0100 |
User-agent: |
Mutt/1.4i |
On Tue, Dec 03, 2002 at 08:29:20PM -0800, Thomas Bushnell, BSG wrote:
> Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
>
> > > Also, it seems worthwhile to make it possible to have a hole. Maybe you
> > > intended that but didn't say. e.g. an object[i] that is MACH_PORT_NULL
> > > means a hole at start[i].
> >
> > Well, I did say it:
> >
> > "Note that you can specify MACH_PORT_NULL as a memobj if you want a hole."
>
> That's wrong, however. MACH_PORT_NULL, as a memory object, does not
> mean "no object", it means "anonymously allocated memory". You
> shouldn't overload that meaning, even if you can't (or don't want to
> bother) providing the interface that it would mean.
Mmh, I was actually thinking of a hole as being anonymously allocated
memory, ie, zero filled.
Do we really need actual holes, ie, invalid pages? Can we use
MACH_PORT_DEAD?
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org marcus@gnu.org
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/
Re: proxy memory objects patch, Marcus Brinkmann, 2002/12/03