Subject: Re: compat mmap behavior
To: Jaromir Dolecek <email@example.com>
From: Andrew Brown <firstname.lastname@example.org>
Date: 01/28/2003 14:27:41
>I don't see any reason to keep the extra compat code.
>Would be good to g/c, IMO.
>> i can see why it might be done in svr4_32_sys_mmap(), maybe in
>> svr4_32_sys_mmap64(), and sunos32_sys_mmap(). they're designed to
>> operate in a mixed 32/64 bit environment, right?
>> the way that px_mmap_info() works is similar, but different in that it
>> calls on uvm_mmap() to do the work, so it needs to pick a reasonable
>> default itself, though i wonder if it couldn't be converted to use
>> sys_mmap() instead.
can anyone comment on these? perhaps either assert that they need to
stay as they are, or tell me if they can be "converted" as well?
|-----< "CODE WARRIOR" >-----|
email@example.com * "ah! i see you have the internet
firstname.lastname@example.org (Andrew Brown) that goes *ping*!"
email@example.com * "information is power -- share the wealth."