Hi. On Friday 24 March 2006 03:02, Linux Kernel Mailing List wrote: > commit 61159a314bca6408320c3173c1282c64f5cdaa76 > tree 8e1b7627443da0fd52b2fac66366dde9f7871f1e > parent f577eb30afdc68233f25d4d82b04102129262365 > author Rafael J. Wysocki <[email protected]> Thu, 23 Mar 2006 19:00:00 -0800 > committer Linus Torvalds <[email protected]> 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 <[email protected]> > Acked-by: Pavel Machek <[email protected]> > Signed-off-by: Andrew Morton <[email protected]> > Signed-off-by: Linus Torvalds <[email protected]> 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:
pgpBukD8HNWls.pgp
Description: PGP signature
- Follow-Ups:
- Re: [PATCH] swsusp: separate swap-writing/reading code
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [PATCH] swsusp: separate swap-writing/reading code
- Prev by Date: [PATCH] Dont build altivec raid on x86
- Next by Date: Re: [PATCH] Dont build altivec raid on x86
- Previous by thread: [patch 00/13] Cell kernel updates
- Next by thread: Re: [PATCH] swsusp: separate swap-writing/reading code
- Index(es):
 |