Date:	Wed, 27 Sep 2000 09:06:31 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Edmund Horner <ejrh AT paradise DOT net DOT nz>
cc:	djgpp AT delorie DOT com
Subject:	Re: C Library: mmap() function
In-Reply-To:	<970034480.596718@shelley.paradise.net.nz>
Message-ID:	<Pine.SUN.3.91.1000927085805.456A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 27 Sep 2000, Edmund Horner wrote:

> I understand that DPMI is not supposed to provide support for mmap().  Can
> we extend it?

DPMI is a spec for a programming environment and an API.  As such, we 
cannot change the DPMI spec.  We can, in principle, change at least one 
implementation of the spec (see below).

> Windows: does DJGPP under Windows rely on the OS for virtual memory
> management?

Windows includes a built-in DPMI server that supports DPMI v0.9 and 
virtual memory.  DJGPP uses that DPMI server when DJGPP programs run on 
Windows.  You cannot run DPMI programs on Windows except by using 
Windows' own DPMI server.

> If so, then there's probably not much to be done about it,
> right?

In practice, no.

> CSDPMI: can this server be extended to provide mmap() functionality?

CWSDPMI is Free Software, so you can do anything you want with it.

However, it is still not clear to me what parts of mmap do you need, and 
for what purposes.  As I've written elsewhere in this thread, mmap can be 
used for several different purposes, and some of them can be emulated 
without the need to change CWSDPMI or mess with the DPMI issues.  So 
please consider explaining a bit more about your specific needs; perhaps 
there are alternative solutions to those needs.

- Raw text -