All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Kevin Fenzi <kevin@scrye.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc2-mm1 swsusp bug report.
Date: Mon, 27 Sep 2004 07:59:42 +1000	[thread overview]
Message-ID: <1096235982.10015.1.camel@desktop.cunninghams> (raw)
In-Reply-To: <20040926100442.GG10435@elf.ucw.cz>

Hi.

On Sun, 2004-09-26 at 20:04, Pavel Machek wrote:
> > Are we still planning on having suspend2 replace swsusp eventually? It
> > was a lot of work to switch from those high order allocations, and if we
> > are still going to replace swsusp, perhaps it's would be a better use of
> > your time to do other things?
> 
> I do not know if I'm more scared of swsusp1 to kill order-8
> allocations or if suspend2's two page sets scare me more. (Hooks
> suspend2 needs to stop all page cache activity are scary...)

Hooks to stop all page cache activity? I'm not sure what you mean.

> I certainly want some parts of suspend2 (like improved freezer, if it
> can be made small enough), but I'm no longer sure I want all of it. I
> expected many people complaining about highmem problems in swsusp1,
> and that just did not happen; SMP support turned out to be reasonably
> simple...

Okay. There are other advantages too, of course :>

Nigel


  reply	other threads:[~2004-09-26 21:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  2:19 2.6.9-rc2-mm1 swsusp bug report Kevin Fenzi
2004-09-24 14:37 ` Pavel Machek
2004-09-24 21:09   ` Kevin Fenzi
2004-09-24 23:40     ` Nigel Cunningham
2004-09-25  1:45       ` Kevin Fenzi
2004-09-25 11:53         ` Nigel Cunningham
2004-09-25 12:22           ` Nick Piggin
2004-09-25 12:56             ` William Lee Irwin III
2004-09-25 13:21               ` Nigel Cunningham
2004-09-25 12:56             ` Nigel Cunningham
2004-09-25 13:38               ` Nick Piggin
2004-09-25 13:03             ` Nigel Cunningham
2004-09-25 15:45             ` Pavel Machek
2004-09-25 22:03               ` Nigel Cunningham
2004-09-26 10:04                 ` Pavel Machek
2004-09-26 21:59                   ` Nigel Cunningham [this message]
2004-09-26 22:43                     ` Pavel Machek
2004-09-27 10:12                       ` Nigel Cunningham
2004-09-26 16:18           ` Marcelo Tosatti
2004-09-26 18:39             ` Pavel Machek
2004-09-25 10:15     ` Pavel Machek
     [not found] <2HO0C-4xh-29@gated-at.bofh.it>
     [not found] ` <2I5b2-88s-15@gated-at.bofh.it>
     [not found]   ` <2I5E5-6h-19@gated-at.bofh.it>
     [not found]     ` <2I7Zd-1TK-11@gated-at.bofh.it>
2004-09-25  1:05       ` Pascal Schmidt
2004-09-25 10:16         ` Pavel Machek
2004-10-10 18:17           ` Jan Rychter
2004-10-11 13:32             ` Pavel Machek
2004-10-11 14:53               ` Jan Rychter
2004-10-17 19:10                 ` Pavel Machek
2004-10-17 21:40                   ` Nigel Cunningham
2004-10-11  9:56           ` Stefan Seyfried
2004-10-11 14:59             ` Pavel Machek
2004-10-11 17:18               ` Stefan Seyfried
2004-10-11 19:58                 ` Rafael J. Wysocki
2004-10-12  8:55                   ` Pavel Machek
2004-10-13 17:29                     ` 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=1096235982.10015.1.camel@desktop.cunninghams \
    --to=ncunningham@linuxmail.org \
    --cc=kevin@scrye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pavel@suse.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.