From: William Lee Irwin III <wli@holomorphy.com>
To: Amir Hermelin <amir@montilio.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PG_reserved bug
Date: Wed, 26 Nov 2003 05:09:27 -0800 [thread overview]
Message-ID: <20031126130927.GM8039@holomorphy.com> (raw)
In-Reply-To: <004501c3b41e$38b3c570$1d01a8c0@CARTMAN>
On Wed, Nov 26, 2003 at 03:07:13PM +0200, Amir Hermelin wrote:
> Can't I just not use the reserved bit (therefore effectively use the
> refcount), and keep the minimal count at 1 or 2? Will that have the same
> effect as setting the reserved bit?
You can do that, yes. There are certain disadvantages to doing so, e.g.
poor interactions with higher-order allocations.
-- wli
prev parent reply other threads:[~2003-11-26 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 10:09 PG_reserved bug Amir Hermelin
2003-11-26 10:17 ` William Lee Irwin III
2003-11-26 12:45 ` Amir Hermelin
2003-11-26 12:50 ` William Lee Irwin III
2003-11-26 13:07 ` Amir Hermelin
2003-11-26 13:09 ` William Lee Irwin III [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=20031126130927.GM8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=amir@montilio.com \
--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;
as well as URLs for NNTP newsgroup(s).