I discovered to my dismay today that the length field in the mmap call is
a size_t, not an off_t. I was attempting to process a large (~50 MByte) file
and found I was only processing the first 4 MBytes of it.
Is this intentional, or just an artifact of the implementation? Is there any
reason NOT to change this to an off_t?
Granted, I'm no VM hacker, but I'm willing to take a swing at it if there is
any interest in putting it into the system. Otherwise, I have a workaround
that works just fine for this application.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
http://softweyr.com/ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message