mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: syscall __NR_mmap2
Date: Tue, 8 Jul 2003 10:40:15 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307081033190.267@chaos> (raw)
In-Reply-To: <20030708140546.GA15612@mail.jlokier.co.uk>

On Tue, 8 Jul 2003, Jamie Lokier wrote:

> Richard B. Johnson wrote:
> > > The offset argument to mmap2 is divided by PAGE_SIZE.
> > > That is the whole point of mmap2 :)
> >
> > Okay. Do you know where that's documented? Nothing in linux/Documentation,
> > and nothing in any headers. Do you have to read the code to find out?
> >
> > So, the address is now the offset in PAGES, not bytes. Seems logical,
> > but there is no clue in any documentation.
>
> I found this great command which really helps.  Only 1337 kernel
> gnurus know about it, now u can be 1 2 :)
>
> $ man mmap2
> [...]
>        The  function mmap2 operates in exactly the same way as mmap(2), except
>        that the final argument specifies the offset into the file in units  of
>        the  system  page  size  (instead of bytes).
>
> -- Jamie
>

Yeah? So the Linux kernel now requires a specific vendor distribution?
Since when?

So, to get the proper documentation of the Linux Kernel, I now
need to purchase a vendor's distribution??? I think not. I think
the sys-calls need to be documented and I think that I have established
proof of that supposition.

Script started on Tue Jul  8 10:35:05 2003
# man mmap2
No manual entry for mmap2
# mmap
# man map

MMAP(2)             Linux Programmer's Manual             MMAP(2)

NAME
       mmap, munmap - map or unmap files or devices into memory

SYNOPSIS
       #include <sys/types.h>
       #include <sys/mman.h>

       caddr_t  mmap(caddr_t  addr,  size_t  len,  int prot , int
       flags, int fd, off_t offset );
       int munmap(caddr_t addr, size_t len);

DESCRIPTION
       WARNING: This is a BSD man page.  Linux 0.99.11 can't  map
       files, and can't do other things documented here.

       The  mmap  function  causes the pages starting at addr and
       continuing for at most len bytes to  be  mapped  from  the
       object  described  by  fd, starting at byte offset offset.
       If offset or len is not a multiple of  the  pagesize,  the
       mapped region may extend past the specified range.

line 1
#
#
# exit
exit

Script done on Tue Jul  8 10:35:29 2003

Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


  reply	other threads:[~2003-07-08 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-07 21:00 Richard B. Johnson
2003-07-07 21:32 ` Ulrich Drepper
2003-07-08 11:56   ` Richard B. Johnson
2003-07-08  0:36 ` Jamie Lokier
2003-07-08 11:54   ` Richard B. Johnson
2003-07-08 13:59     ` Kurt Wall
2003-07-08 14:05     ` Jamie Lokier
2003-07-08 14:40       ` Richard B. Johnson [this message]
2003-07-08 14:49         ` Randy.Dunlap
2003-07-08 14:51         ` Kurt Wall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.53.0307081033190.267@chaos \
    --to=root@chaos.analogic.com \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®