All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH -mm] swsusp: Use rbtree for tracking allocated swap
Date: Mon, 9 Apr 2007 15:03:56 +0200	[thread overview]
Message-ID: <200704091503.57424.rjw@sisk.pl> (raw)
In-Reply-To: <1176066445.10725.123.camel@nigel.suspend2.net>

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

  reply	other threads:[~2007-04-09 13:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07 21:20 [RFC][PATCH -mm] swsusp: Use rbtree for tracking allocated swap Rafael J. Wysocki
2007-04-07 22:06 ` Andrew Morton
2007-04-07 22:31   ` Nigel Cunningham
2007-04-07 23:13     ` Rafael J. Wysocki
2007-04-07 23:42       ` Nigel Cunningham
2007-04-08 16:47         ` Rafael J. Wysocki
2007-04-08 21:07           ` Nigel Cunningham
2007-04-09 13:03             ` Rafael J. Wysocki [this message]
2007-04-09 21:00               ` Nigel Cunningham
2007-04-08 12:56 ` Pavel Machek
2007-04-08 17:02   ` Rafael J. Wysocki
2007-04-09 12:39     ` Pavel Machek
2007-04-10 21:00       ` 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=200704091503.57424.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    /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.