Re: [patch] mmap2.2: add definition of mmap64

["Марк Коренберг" <socketpair-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

2009/11/15 Petr Baudis <pasky-+ZI9xUNit7I@public.gmane.org>:
> On Sat, Nov 14, 2009 at 09:38:00PM +0500, Марк Коренберг wrote:
>> mmap64 in ubuntu is symlink to mmap2, but no actual definition of
>> mmap64 in man page (!).
>
>> --- mmap2.2.was       2008-12-06 08:55:24.000000000 +0500
>> +++ mmap2.2   2009-11-11 12:27:26.000000000 +0500
>> @@ -33,8 +33,12 @@
>>  .nf
>>  .B #include <sys/mman.h>
>>  .sp
>> +.B /* Linux syscall */
>>  .BI "void *mmap2(void *" addr ", size_t " length ", int " prot ,
>>  .BI "             int " flags ", int " fd ", off_t " pgoffset );
>> +.sp
>> +.BI "void *mmap64(void *" addr ", size_t " length ", int " prot ,
>> +.BI "             int " flags ", int " fd ", off64_t " byteoffset );
>>  .fi
>>  .SH DESCRIPTION
>>  The
>
> Then there should be also some word in the manpage about what mmap64()
> actually is?
>
> --
>                                Petr "Pasky" Baudis
> A lot of people have my books on their bookshelves.
> That's the problem, they need to read them. -- Don Knuth
>
Reading 'man mmap2' is what I want. I understood all I need. I can't
build correct (in English) sentences, describing mmap64, but I want
this be specified:
1. mmap2 now can use offsets with 32+12=44 bits long, and not 64 ! if
bigger offset specified, results are undefined.
2. file 'fd' should be opened with O_LARGEFILE for offsets bigger than 4GB? 2GB?
3. mmap64 is libc wrapper around mmap2 syscall.
4. Dont't know, but special #define should be used in order to use
64-bit-offset functions.

-- 
Segmentation fault
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html