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

RE: [MiNT] memory fragmentation



> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Jo-Even.Skarstein@gjensidige.no
> Sent: Wednesday, August 18, 1999 9:55 AM
> To: mint@fishpool.com
> Subject: RE: [MiNT] memory fragmentation
> 
> 
> > -----Original Message-----
> > From:	Julian Reschke [SMTP:reschke@muenster.de]
> > Sent:	Tuesday, August 17, 1999 10:13 PM
> > To:	gryf@hrzpub.tu-darmstadt.de; MiNT mailing list
> > Subject:	RE: [MiNT] memory fragmentation
> > 
> > Well -- any memory which is Mxalloc'ed as non-private needs to 
> reside in a
> > global memory space. Where's the problem???
> > 
> What about userdefs? What happens with these when the application and the
> AES runs in different virtual memory-spaces?

Good question. Userdef code might have to run in global memory.