public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Waitz <tali@admingilde.org>
To: Paul Drynoff <pauldrynoff@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmalloc man page before 2.6.17
Date: Sat, 27 May 2006 12:28:05 +0200	[thread overview]
Message-ID: <20060527102804.GD14325@admingilde.org> (raw)
In-Reply-To: <36e6b2150605260344l1ba91d56we2d224d49bde4d8e@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]

hoi :)

thank you for your work!

unfortunately gmail seems to have corrupted your patch slightly
(single spaces on it's own line are stripped).

On Fri, May 26, 2006 at 02:44:08PM +0400, Paul Drynoff wrote:
> +/**
> + * kmalloc - allocate memory
> + * @size: how many bytes of memory are required.
> + * @gfp: the type of memory to allocate.

this should be @flags

> + * kmalloc is the normal method of allocating memory
> + * in the kernel.
> + *
> + * The @gfp argument may be one of:
> + *
> + * %GFP_USER - Allocate memory on behalf of user.  May sleep.
> + *
> + * %GFP_KERNEL - Allocate normal kernel ram.  May sleep.
> + *
> + * %GFP_ATOMIC - Allocation will not sleep.  Use inside interrupt handlers.
> + * %GFP_HIGHUSER - Allocate pages from high memory.
> + * %GFP_NOIO - Do not do any I/O at all while trying to get memory.
> + * %GFP_NOFS - Do not make any fs calls while trying to get memory.

please add newlines here, too.

> + * Also it is possible set different flags by OR'ing
> + * in one or more of the following:
> + * %__GFP_COLD
> + *  - Request cache-cold pages instead of trying to return cache-warm 
> pages.
> + * %__GFP_DMA
> + *  - Request memory from the DMA-capable zone
> + * %__GFP_HIGH
> + *  - This allocation is high priority and may use emergency pools.
> + * %__GFP_HIGHMEM
> + *   - Allocated memory may be from highmem.
> + * %__GFP_NOFAIL
> + *  - Indicate that this allocation is in no way allowed to fail
> + * (think twice before using).
> + * %__GFP_NORETRY
> + * - If memory is not imidiately available, then give up at once.
> + * %__GFP_NOWARN
> + * - If allocation fails, don't issue any warnings.
> + * %__GFP_REPEAT
> + * - If allocation fails initially, try once more before failing.

and here, too.

-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-05-27 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26  7:07 [PATCH] kmalloc man page before 2.6.17 Paul Drynoff
2006-05-26  7:17 ` Pekka Enberg
2006-05-26  7:58   ` Paul Drynoff
2006-05-26  8:03     ` Pekka J Enberg
2006-05-26  8:20       ` Paul Drynoff
2006-05-26  9:42         ` Andrey Panin
2006-05-26  9:48         ` Jesper Juhl
2006-05-26 10:44           ` Paul Drynoff
2006-05-26 13:23             ` Paulo Marques
2006-05-26 14:17             ` Christoph Lameter
2006-05-26 14:55               ` Paul Drynoff
2006-05-26 15:03                 ` Christoph Lameter
2006-05-26 19:55             ` Luca
2006-05-27 10:28             ` Martin Waitz [this message]
2006-05-26 10:47           ` Paul Drynoff

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=20060527102804.GD14325@admingilde.org \
    --to=tali@admingilde.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pauldrynoff@gmail.com \
    /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