From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Andrew Morton <akpm@digeo.com>
Cc: David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, jgarzik@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: extra PG_* bits for page->flags
Date: Tue, 11 Feb 2003 13:07:14 +1300 [thread overview]
Message-ID: <1044922034.4866.14.camel@laptop-linux.cunninghams> (raw)
In-Reply-To: <20030210151244.7e42d3fb.akpm@digeo.com>
On Tue, 2003-02-11 at 12:12, Andrew Morton wrote:
> David Howells <dhowells@redhat.com> wrote:
> > (*) PG_journal
> > (*) PG_journalmark
>
> Well. If you new fs goes in then yes, we can spare those bits (just).
May I ask, how many bits do you consider available? swsusp beta 18 (ie
2.4), which I'm beginning to port to 2.5, uses 4 bits during suspend &
resume for various purposes. If I understand the code correctly, the
zone flags use bits 24-31 (although there has been that thread saying
they could use less bits). I see in the 2.5.60 patch bit 19 is now in
use. Should I be using private, temporarily allocated bitmaps instead of
the page flags, to ease the pressure? (Especially since the suspend code
is not used in 'normal' operation anyway).
Regards,
Nigel
next prev parent reply other threads:[~2003-02-10 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 10:51 extra PG_* bits for page->flags David Howells
2003-02-10 23:12 ` Andrew Morton
2003-02-11 0:07 ` Nigel Cunningham [this message]
2003-02-11 0:20 ` Andrew Morton
2003-02-11 2:17 ` Nigel Cunningham
2003-02-11 4:18 ` Valdis.Kletnieks
2003-02-11 11:05 ` David Howells
2003-02-11 10:54 ` David Howells
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=1044922034.4866.14.camel@laptop-linux.cunninghams \
--to=ncunningham@clear.net.nz \
--cc=akpm@digeo.com \
--cc=dhowells@redhat.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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