From: Nigel Cunningham <ncunningham@cyclades.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC][PATCH] Dynamically allocated pageflags.
Date: Sat, 19 Feb 2005 14:35:22 +1100 [thread overview]
Message-ID: <1108784122.4077.123.camel@desktop.cunningham.myip.net.au> (raw)
In-Reply-To: <1108782127.19253.4.camel@localhost>
Hi.
On Sat, 2005-02-19 at 14:02, Dave Hansen wrote:
> On Sat, 2005-02-19 at 13:43 +1100, Nigel Cunningham wrote:
> > For some time now, we've been running out of bits for pageflags.
> >
> > In Suspend2, I need the functional equivalent of pageflags, but don't
> > need them when Suspend isn't running. One of the outcomes of the last
> > submission of Suspend2 for review was that I changed the format in which
> > that data is stored, creating something I call dynamically allocated
> > pageflags.
> >
> > It's a simple idea: we tie together a bunch of order zero allocated
> > pages using a kmalloc'd list of poiinters to those pages, and store the
> > location of that kmalloc'd list in what's really an unsigned long **
> > (typedef'd). We also provide macros so that calls for setting and
> > clearing flags can look just like ordinary pageflag set/clear/test
> > invocations.
> >
> > Helpers are also provided for allocating and freeing the maps.
>
> I'm kicking myself because I thought about this 2 minutes after we
> talked on IRC.
> One issue is that it doesn't work with DISCONTIGMEM (or the upcoming
> sparsemem). max_mapnr doesn't exist on those systems, and on the really
> discontiguous ones, you might be allocating very large areas with very
> sparse maps.
:> Am I right in thinking that just requires something similar, done
per-zone? If that's the case, I'll happily modify the code to suit. I
should support discontig anyway in suspend.
> One thing that I've been thinking about for these things is something
> tree-based. A 1 or 2-level tree, like pagetables should be fast enough,
> and handle the sparse and discontiguous layouts a little better than a
> flat one. We could even do a flat bitmap for normal systems, and #ifdef
> in the table only when it's needed. I can take a look at doing this
> next week.
Mmm. I've got enough on my plate at the mo, so I'll just wait to see
what you come up with.
Regards,
Nigel
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574
next prev parent reply other threads:[~2005-02-19 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 2:43 Nigel Cunningham
2005-02-19 3:02 ` Dave Hansen
2005-02-19 3:35 ` Nigel Cunningham [this message]
2005-02-19 5:51 ` Dave Hansen
2005-02-19 6:03 ` Nigel Cunningham
2005-02-21 18:15 ` Dave Hansen
2005-02-19 9:50 ` Pavel Machek
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=1108784122.4077.123.camel@desktop.cunningham.myip.net.au \
--to=ncunningham@cyclades.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®