linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
To: Chirayu Patel <chirayu@wipro.tcpn.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: __free_page() and free_pages() - Differences?
Date: Mon, 23 Mar 1998 21:20:06 GMT	[thread overview]
Message-ID: <199803232120.VAA02077@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <Pine.SUN.3.95.980322184553.3977Z-100000@Kabini>

Hi,

On Sun, 22 Mar 1998 18:57:28 +0530 (GMT+0530), Chirayu Patel
<chirayu@wipro.tcpn.com> said:

> Hi ,
> I am having trouble understanding the difference between 
> the __free_page function and free_pages function in page_alloc.c

They are identical functions with different calling conventions.  When
we are freeing a page, we often have a page struct already in hand, so
__free_page is an alternative way of freeing a page which avoids the
unnecessary page map lookup.

--Stephen

      reply	other threads:[~1998-03-23 23:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-22 13:27 Chirayu Patel
1998-03-23 21:20 ` Stephen C. Tweedie [this message]

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=199803232120.VAA02077@dax.dcs.ed.ac.uk \
    --to=sct@dcs.ed.ac.uk \
    --cc=chirayu@wipro.tcpn.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.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