From: Nigel Cunningham <ncunningham@cyclades.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-mm <linux-mm@kvack.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamically allocated pageflags
Date: Thu, 9 Feb 2006 09:43:21 +1000 [thread overview]
Message-ID: <200602090943.25550.ncunningham@cyclades.com> (raw)
In-Reply-To: <200602021431.30194.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
Hi.
On Thursday 02 February 2006 23:31, Andi Kleen wrote:
> On Thursday 02 February 2006 12:11, Nigel Cunningham wrote:
> > Hi everyone.
> >
> > This is my latest revision of the dynamically allocated pageflags patch.
> >
> > The patch is useful for kernel space applications that sometimes need to flag
> > pages for some purpose, but don't otherwise need the retain the state. A prime
> > example is suspend-to-disk, which needs to flag pages as unsaveable, allocated
> > by suspend-to-disk and the like while it is working, but doesn't need to
> > retain any of this state between cycles.
>
> It looks like total overkill for a simple problem to me. And is there really
> any other user of this other than swsusp?
Sorry for the slow response. I switched email clients and gained a bogus
filter along the way (entirely my fault, of course).
As Dave said, he might make use of them too. I use about 5 or 6 of these,
depending upon exactly how Suspend2 is configured.
In the meanwhile, AKPM gave me a suggestion for a better solution
(radix-trees). My algorithms & data-structures course was 14 years ago,
so I'll go dust off Kingston (IIRC) and learn what he's talking about again :)
Thanks for the feedback and regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-08 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 11:11 Nigel Cunningham
2006-02-02 13:31 ` Andi Kleen
2006-02-02 16:47 ` Dave Hansen
2006-02-08 23:43 ` Nigel Cunningham [this message]
2006-02-09 7:00 ` Magnus Damm
2006-02-09 7:08 ` Nigel Cunningham
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=200602090943.25550.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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