From: Nikita Danilov <nikita@clusterfs.com>
To: Andrew Morton <akpm@osdl.org>
Cc: pbadari@us.ibm.com, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: page flags ?
Date: Thu, 19 May 2005 18:37:00 +0400 [thread overview]
Message-ID: <17036.42124.398130.730456@gargle.gargle.HOWL> (raw)
In-Reply-To: <20050519041116.1e3a6d29.akpm@osdl.org>
Andrew Morton writes:
> Andy Whitcroft <apw@shadowen.org> wrote:
> >
> > > How many bits are spare now? ZONETABLE_PGSHIFT hurts my brain.
> >
> > The short answer is that on 32 bit architectures there are 24 bits
> > allocated to general page flags, page-flags.h indicates that 21 are
> > currently assigned so assuming it is accurate there are currently 3 bits
> > free.
>
> Yipes, I didn't realise we were that close.
>
> We can reclaim PG_highmem, use page_zone(page)->highmem
>
> We can probably reclaim PG_slab
>
> We can conceivably reclaim PG_swapcache, although that stuff got ugly.
>
> Would dearly love to nuke PG_reserved, but everybody's scared of that ;)
>
> PG_uncached is currently ia64-only and could conceivably be moved to bit
> 32, except there are rumours that arm might want to use it someday.
>
> It's a bit irritating that swsusp uses two flags.
>
> I don't see any other low-hanging fruit there.
Things like PG_uptodate and PG_error can be moved to the radix-tree tags
after checking that they are used only for pages in the mapping, which
seems to be the case.
> --
Nikita.
next prev parent reply other threads:[~2005-05-19 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 21:13 page flags ? Badari Pulavarty
2005-05-18 21:56 ` Andrew Morton
2005-05-18 22:42 ` Badari Pulavarty
2005-05-18 23:23 ` Andrew Morton
2005-05-19 0:09 ` Badari Pulavarty
2005-05-19 0:26 ` Chandra Seetharaman
2005-05-19 1:36 ` Dave Hansen
2005-05-19 10:51 ` Andy Whitcroft
2005-05-19 11:11 ` Andrew Morton
2005-05-19 14:37 ` Nikita Danilov [this message]
2005-05-19 18:29 ` Badari Pulavarty
2005-05-19 22:53 ` Andrew Morton
2005-05-19 23:34 ` Badari Pulavarty
2005-05-20 0:03 ` Martin J. Bligh
2005-05-19 23:55 ` Badari Pulavarty
2005-05-20 0:20 ` Martin J. Bligh
2005-05-18 23:57 ` Bryan Henderson
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=17036.42124.398130.730456@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.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;
as well as URLs for NNTP newsgroup(s).