delorie.com/archives/browse.cgi | search |
Date: | Thu, 11 May 2000 09:25:14 -0400 (EDT) |
Message-Id: | <200005111325.JAA13157@indy.delorie.com> |
From: | Eli Zaretskii <eliz AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <200005101311.JAA30165@envy.delorie.com> (message from DJ Delorie |
on Wed, 10 May 2000 09:11:36 -0400) | |
Subject: | Re: Perfomance of gc-simple |
References: | <200005091512 DOT LAA22852 AT qnx DOT com> <200005091906 DOT PAA10862 AT indy DOT delorie DOT com> <200005091956 DOT PAA28210 AT envy DOT delorie DOT com> <200005101217 DOT IAA11786 AT indy DOT delorie DOT com> <200005101311 DOT JAA30165 AT envy DOT delorie DOT com> |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> Date: Wed, 10 May 2000 09:11:36 -0400 > From: DJ Delorie <dj AT delorie DOT com> > > > > Plus, individual mmap'd regions can be grown as needed. > > > > How would this be implemented, typically? Growing a memory region > > should need to relocate it, at least sometimes, no? It sounds a lot > > like realloc, unless I'm missing something. > > mmap'd regions are placed far away from each other, say one every > 256MB, with big unmapped gaps between them. This is obviously impossible under DPMI 0.9. However, except for performance, realloc should do the same. If growing mmap'ed region is not a frequent operation, perhaps we could get away with that.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |