From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH 0/5] Dynamically allocated pageflags.
Date: Tue, 24 Jul 2007 08:27:18 +1000 [thread overview]
Message-ID: <200707240827.18807.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <200707240005.22163.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
Hi.
On Tuesday 24 July 2007 08:05:21 Rafael J. Wysocki wrote:
> Hi,
>
> On Monday, 23 July 2007 15:05, Nigel Cunningham wrote:
> > Hi all.
> >
> > As we all know, pageflags have been a scarce resource for a while now.
These
> > patches seek to help address that issue by adding support for a new type
> > of 'dynamically allocated' pageflag.
> >
> > The basic idea is that we use per node & zone bitmaps built out of order
zero
> > allocations, to replace bits in page->flags. Bitmaps can be sparse, being
> > populated when a bit on the page is set, and returning zero for all bits
in
> > sparse pages. Untested hotplug support is included.
> >
> > This method of storing the data does of course come with a performance
hit.
> > I've included some simple timing loops in #ifdef'd code that help quantify
> > that.
> >
> > Interestingly, the new implementation is actually quicker under some
> > circumstances. In cases where the usage pattern involves operating on the
> > flags for a number of pages in succession, the hit involved in getting the
> > struct pages from main memory appears to be greater than that involved in
> > calculating which unsigned long and bit to test.
> >
> > Tested only on UP (x86_64) so far.
>
> How does it compare to the memory bitmaps used by swsusp, defined in
> kernel/power/snapshot.c?
Looking through kernel/power/snapshot.c, I'd say this implementation has
advantages in having support for memory hotplugging, sparseness and random
access to the flags in the bitmap. Like the snapshot.c implementation, it
uses per-zone bitmaps and has a method that can be used to iterate over the
contents of a bitmap. Having per-node support might also be useful. I haven't
looked at the speed of the snapshot.c implementation. Do you see advantages
to snapshot.c that I might have missed?
Regards,
Nigel
--
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-23 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 13:05 [RFC] [PATCH 0/5] Dynamically allocated pageflags Nigel Cunningham
2007-07-23 13:15 ` [RFC] [PATCH 3/5] Dynamically allocated pageflags - PageSwapCache conversion Nigel Cunningham
2007-07-23 13:16 ` [RFC] [PATCH 4/5] Dynamically allocated pageflags - PageSlab conversion Nigel Cunningham
2007-07-23 13:17 ` [RFC] [PATCH 2/5] Dynamically allocated pageflags - PageMappedToDisk conversion Nigel Cunningham
2007-07-23 13:17 ` [RFC] [PATCH 5/5] Dynamically allocated pageflags - PageBuddy conversion Nigel Cunningham
2007-07-23 13:25 ` [RFC] [PATCH 0/5] Dynamically allocated pageflags Nigel Cunningham
2007-07-23 14:29 ` Arjan van de Ven
2007-07-23 21:52 ` Nigel Cunningham
2007-07-23 22:05 ` Rafael J. Wysocki
2007-07-23 22:27 ` Nigel Cunningham [this message]
2007-07-24 9:47 ` Rafael J. Wysocki
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=200707240827.18807.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@suspend2.net \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.