From:	"Edmund Horner" <ejrh AT paradise DOT net DOT nz>
Newsgroups:	comp.os.msdos.djgpp
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000926172717 DOT 15724A-100000 AT is>
Subject:	Re: C Library: mmap() function
Lines:	32
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Organization:	Paradise Net
Message-ID:	<970034480.596718@shelley.paradise.net.nz>
Cache-Post-Path:	shelley.paradise.net.nz!unknown AT 203-79-65-227 DOT tnt8 DOT paradise DOT net DOT nz
X-Cache:	nntpcache 2.4.0b5 (see http://www.nntpcache.org/)
Date:	Wed, 27 Sep 2000 18:04:11 +1200
NNTP-Posting-Host:	203.96.152.26
X-Complaints-To:	newsadmin AT xtra DOT co DOT nz
X-Trace:	news.xtra.co.nz 970034481 203.96.152.26 (Wed, 27 Sep 2000 18:01:21 NZST)
NNTP-Posting-Date:	Wed, 27 Sep 2000 18:01:21 NZST
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

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

Windows: does DJGPP under Windows rely on the OS for virtual memory
management?  If so, then there's probably not much to be done about it,
right?

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

Edmund.

"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> wrote in message
news:Pine DOT SUN DOT 3 DOT 91 DOT 1000926172717 DOT 15724A-100000 AT is...
>
> On Wed, 27 Sep 2000, Edmund Horner wrote:
>
> > Can the mmap() function be implemented in the DJGPP libc?
>
> Yes, but only for allocating memory and then only for some values of
> the arguments.  For example, memory-mapped files cannot be supported,
> and MAP_FIXED in the flags will not work (since the DPMI client has no
> control on the address where memory is allocated).
>
> > If so, would it be a simple port from, say, the Linux glibc source, or
would
> > it (as I suspect) involve a lot of fiddling with DPMI?
>
> I cannot imagine that a Linux source will be a good starting point,
> since Linux uses a totally different memory organization and protection
> methods.

- Raw text -