mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Memory allocation question
Date: Wed, 21 Nov 2001 12:13:09 -0800	[thread overview]
Message-ID: <3BFC0AD5.5A4802D@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111211651280.1491-100000@duckman.distro.conectiva>

Rik van Riel wrote:
> 
> On Wed, 21 Nov 2001, george anzinger wrote:
> > Alan Cox wrote:
> > >
> > > > size chuncks.  Currently I am using kmalloc() to allocate a page at a
> > > > time.  I don't want to have to worry about mapping/unmapping etc.  I
> > >
> > > Use get_free_page() to get page sized chunks
> >
> > What about __get_free_page() ?  I don't need or want the clear page
> > (performance issues).
> 
> get_free_page() doesn't clear the page afaics.
> 
In mm.h (2.4.13 kernel)....

#define __get_free_page(gfp_mask) \
		__get_free_pages((gfp_mask),0)

#define __get_dma_pages(gfp_mask, order) \
		__get_free_pages((gfp_mask) | GFP_DMA,(order))

/*
 * The old interface name will be removed in 2.5:
 */
#define get_free_page get_zeroed_page
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Where as __get_free_page() does not zero.  I know this is an old kernel,
but...


What am I missing?
-- 
George           george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/

  reply	other threads:[~2001-11-21 20:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 19:23 george anzinger
2001-11-19 19:50 ` Alan Cox
2001-11-21 18:47   ` george anzinger
2001-11-21 18:51     ` Rik van Riel
2001-11-21 20:13       ` george anzinger [this message]
2001-11-21 20:25         ` Rik van Riel

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=3BFC0AD5.5A4802D@mvista.com \
    --to=george@mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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®