linux-kernel - Re: [RFC][PATCH -mm] swsusp: Use rbtree for tracking allocated swap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200704091503.57424.rjw@sisk.pl>
Date:	Mon, 9 Apr 2007 15:03:56 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Nigel Cunningham <nigel@...el.suspend2.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Pavel Machek <pavel@....cz>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH -mm] swsusp: Use rbtree for tracking allocated swap

On Sunday, 8 April 2007 23:07, Nigel Cunningham wrote:
[--snip--]
> > > Normal usage in both cases is simply iterating through the list, so I
> > > guess the cost would be approximately the same.
> > > 
> > > Deletion could would include rebalancing for the rb_nodes.
> > 
> > In swsusp the deletions are needed only if there's an error.
> 
> When freeing swap at the end of the cycle?

That depends on what you mean by 'the end'. :-)

We free swap if the image saving fails only, since it's allocated after we've
created the image.  After the resume, the state of swap from before the image
creation is the current one anyway.

Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/