From: Nigel Cunningham <ncunningham@cyclades.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Pavel Machek <pavel@suse.cz>, Rafael Wysoki <rjw@sisk.pl>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] swsusp: separate swap-writing/reading code
Date: Fri, 24 Mar 2006 07:13:36 +1000 [thread overview]
Message-ID: <200603240713.41566.ncunningham@cyclades.com> (raw)
In-Reply-To: <200603231702.k2NH2OSC006774@hera.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Hi.
On Friday 24 March 2006 03:02, Linux Kernel Mailing List wrote:
> commit 61159a314bca6408320c3173c1282c64f5cdaa76
> tree 8e1b7627443da0fd52b2fac66366dde9f7871f1e
> parent f577eb30afdc68233f25d4d82b04102129262365
> author Rafael J. Wysocki <rjw@sisk.pl> Thu, 23 Mar 2006 19:00:00 -0800
> committer Linus Torvalds <torvalds@g5.osdl.org> Thu, 23 Mar 2006 23:38:07
> -0800
>
> [PATCH] swsusp: separate swap-writing/reading code
>
> Move the swap-writing/reading code of swsusp to a separate file.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> Acked-by: Pavel Machek <pavel@ucw.cz>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
I guess I missed this one somehow. Using a bitmap for allocated swap is really
inefficient because the values are usually not fragmented much. Extents would
have been a far better choice.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2006-03-23 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603231702.k2NH2OSC006774@hera.kernel.org>
2006-03-23 21:13 ` Nigel Cunningham [this message]
2006-03-23 21:53 ` [PATCH] swsusp: separate swap-writing/reading code Rafael J. Wysocki
2006-03-23 22:48 ` Mark Lord
2006-03-23 23:39 ` Rafael J. Wysocki
2006-03-27 10:26 ` Pavel Machek
2006-03-27 10:43 ` Nigel Cunningham
2006-03-27 23:15 ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-27 23:36 ` Nigel Cunningham
2006-03-28 1:18 ` regular swsusp flamewar Harald Arnesen
2006-03-28 9:15 ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-28 9:16 ` Pavel Machek
2006-03-28 10:28 ` Nigel Cunningham
2006-03-28 1:16 ` regular swsusp flamewar Harald Arnesen
2006-03-28 9:13 ` Pavel Machek
2006-03-23 23:58 ` [PATCH] swsusp: separate swap-writing/reading code Andrew Morton
2006-03-24 0:32 ` 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=200603240713.41566.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox