[GSOC]Progress Report of MMU support project

[Sebastian Huber]

On 07/12/2011 12:36 PM, Peter Dufault wrote:
> 
> On Jul 12, 2011, at 6:11 , Sebastian Huber wrote:
> 
>> I would not use size_t here since this is used for the size of single objects.
>> I would use uintptr_t instead.
> 
> Isn't this memory range a single object?  It's mappable as a single object via the memory management hardware.

I don't know.  How is it on segmented memory?

> 
> If you look at existing POSIX functions (mmap(), mprotect(), mlock()) the address is a void * and the size is a size_t.

Ok, then let it be size_t.  These memory protection seems to be only useful
with a linear address space.

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.