From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <ncunningham@linuxmail.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH -mm] swsusp: Use rbtree for tracking allocated swap
Date: Sun, 8 Apr 2007 01:13:23 +0200 [thread overview]
Message-ID: <200704080113.24171.rjw@sisk.pl> (raw)
In-Reply-To: <1175985065.10725.20.camel@nigel.suspend2.net>
On Sunday, 8 April 2007 00:31, Nigel Cunningham wrote:
> Hi.
>
> On Sat, 2007-04-07 at 15:06 -0700, Andrew Morton wrote:
> > On Sat, 7 Apr 2007 23:20:39 +0200 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > > This should allow us to reduce the memory usage, practically always, and
> > > improve performance.
> >
> > And does it?
Yes. There are theoretical corner cases in which it may be less efficient
than the current approach, but in the usual situation it is _much_ better.
> It will. I've been using extents for ages, for the same reasons. I don't
> put them in an rb_tree because I view it as less than most efficient,
Actually, I don't agree with that. In the normal situation (ie. one extent is
needed) there is no difference as far as the memory usage or performance
are concerned, but if there are more extents, the rbtree should be more
efficient.
> but it will still be a huge step forward from bitmaps in the normal
> case.
>
> The worst case would be if every second page of swap was in use, so that
> you needed one extent per swap page. In that case, it would use more
> memory than the bitmap, but far, far more common will be the case where
> only one extent is needed for the whole swap partition, because the
> algorithm used by the swap allocator minimises fragmentation.
Exactly.
Greetings,
Rafael
next prev parent reply other threads:[~2007-04-07 23:10 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 [this message]
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
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=200704080113.24171.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--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.