From: "Amir Hermelin" <amir@montilio.com>
To: "'William Lee Irwin III'" <wli@holomorphy.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: PG_reserved bug
Date: Wed, 26 Nov 2003 15:07:13 +0200 [thread overview]
Message-ID: <004501c3b41e$38b3c570$1d01a8c0@CARTMAN> (raw)
In-Reply-To: <20031126125020.GL8039@holomorphy.com>
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?
Amir.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of William Lee Irwin
III
Sent: Wednesday, November 26, 2003 2:50 PM
To: Amir Hermelin
Cc: linux-kernel@vger.kernel.org
Subject: Re: PG_reserved bug
On Wed, Nov 26, 2003 at 02:45:06PM +0200, Amir Hermelin wrote:
> Ok, fair enough. According to what you say, this behavior won't
> change in 2.6. So, I'm still left with my second question: since I do
> access the pages from several places in my module, and I want to use
> the refcount field of the struct page (and not have to wrap the pages
> in another structure) so I know when my page is no longer referenced,
> how can I make sure it's 'safe' to not use the reserved bit?
It looks like you'll have to wrap the pages in another structure. The
refcounts for reserved pages are effectively meaningless.
-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-11-26 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 10:09 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 [this message]
2003-11-26 13:09 ` William Lee Irwin III
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='004501c3b41e$38b3c570$1d01a8c0@CARTMAN' \
--to=amir@montilio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®