public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: syscall documentation
Date: Sun, 09 Feb 2003 21:09:36 -0500	[thread overview]
Message-ID: <3E4709E0.8000104@pobox.com> (raw)
In-Reply-To: <UTC200302062005.h16K5qn23586.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> The note with the above title last week was very successful -
> several people sent man pages. The copyright situation for
> the *xattr pages is not entirely clear yet, but there is
> good hope that it will be soon.
> 
> Let me send five new pages to l-k - maybe someone has
> additions, corrections or comments.
> 
> The first one is alloc_hugepages.2. Below.
> Probably more can be said about hugetlbfs.
> 
> Andries
> aeb@cwi.nl
> 
> ---------
> NAME
>        alloc_hugepages,  free_hugepages  -  allocate or free huge
>        pages
> 
> SYNOPSIS
>        void *alloc_hugepages(int key, void *addr, size_t len, int
>        prot, int flag);
> 
>        int free_hugepages (void *addr);


The other man pages look great.  The above system calls, however, do not 
exist anymore.

This also brings to light that Documentation/vm/hugetlbpage.txt and 
arch/i386/Kconfig want updating, as well as non-ia32 arches...

	Jeff




  parent reply	other threads:[~2003-02-10  2:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 20:05 syscall documentation Andries.Brouwer
2003-02-07 16:31 ` Horst von Brand
2003-02-10  2:09 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07 18:18 Andries.Brouwer

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=3E4709E0.8000104@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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