From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: Patrick Mochel <mochel@digitalimplant.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
david-b@pacbell.net
Subject: Re: suspend2 merge [was Re: [RFC] Fix Device Power Management States]
Date: Wed, 11 Aug 2004 11:13:04 +0200 [thread overview]
Message-ID: <20040811091304.GD674@elf.ucw.cz> (raw)
In-Reply-To: <1092200754.3843.21.camel@laptop.cunninghams>
Hi!
> > I feared big problems with highmem support, but surprisingly, trivial
> > support thats in current code does not cause problems for
> > people. People seem to like pmdisk+swsusp, too...
>
> That will be because you're eating most of the memory anyway; there's
> not problem finding enough memory to copy the Highmem too. I guess that
> once we start seeing people trying to suspend 2GB to disk or you try to
> eat less memory, Highmem will become more of a pain.
Yes, I know. I was just pleased that people do not complain as much as
I expected them to.
> > Now, people like suspend2 even more, and for good reasons: it is
> > extremely fast, it provides nice feedback and its refrigerator is
> > superior.
> >
> > I also realized that suspend2 is fundamentally more complex than
> > swsusp: it introduces additional time period where page cache must not
> > be touched. I did not realize this sooner.
>
> Sorry. I said it in so many ways! It's not really an issue though;
> processes are stopped and suspend's own I/O doesn't touch page
> cache.
Yes, I know it should work, it is just more things that need to be
verified.
> > Now, there are some parts of swsusp that are not quite okay. One of
> > them is refrigerator -- it fails (in non-critical way but still) in
> > some cases where it should not fail. suspend2 seems to have this
> > solved, and I'd like to merge its refrigerator.
>
> I'll submit a patch. I need to look at how you use the refrigerator
> first. I refrigerate processes prior to resuming as well, and might need
> to adjust things if you don't do that. I also need to check it will work
> okay with S3.
Actually, we are not stopping processes prior to resuming, but I'd
call it a bug to be fixed.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-08-11 9:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 10:43 [RFC] Fix Device Power Management States Patrick Mochel
2004-08-09 11:38 ` Pavel Machek
2004-08-09 16:02 ` Patrick Mochel
2004-08-09 21:29 ` Pavel Machek
2004-08-10 5:03 ` Patrick Mochel
2004-08-10 9:43 ` Nigel Cunningham
2004-08-10 10:20 ` Pavel Machek
2004-08-10 22:33 ` Nigel Cunningham
2004-08-10 13:58 ` Patrick Mochel
2004-08-10 22:29 ` Nigel Cunningham
2004-08-10 22:56 ` Patrick Mochel
2004-08-10 23:09 ` Nigel Cunningham
2004-08-10 23:36 ` suspend2 merge [was Re: [RFC] Fix Device Power Management States] Pavel Machek
2004-08-11 0:04 ` Arkadiusz Miskiewicz
2004-08-11 5:05 ` Nigel Cunningham
2004-08-11 9:13 ` Pavel Machek [this message]
2004-08-10 10:13 ` [RFC] Fix Device Power Management States Pavel Machek
2004-08-10 18:36 ` David Brownell
2004-08-10 20:36 ` Pavel Machek
2004-08-10 22:42 ` Patrick Mochel
2004-08-09 22:15 ` Nigel Cunningham
2004-08-10 0:43 ` Benjamin Herrenschmidt
2004-08-10 9:00 ` Russell King
2004-08-10 10:08 ` Pavel Machek
2004-08-10 0:40 ` Benjamin Herrenschmidt
2004-08-10 4:55 ` Patrick Mochel
2004-08-10 6:52 ` Benjamin Herrenschmidt
2004-08-10 10:07 ` Pavel Machek
2004-08-10 14:28 ` Patrick Mochel
2004-08-10 17:56 ` Pavel Machek
2004-08-10 22:41 ` Patrick Mochel
2004-08-10 23:10 ` Pavel Machek
2004-08-10 23:14 ` [patch] Smaller goal first: fix confusion [was Re: [RFC] Fix Device Power Management States] Pavel Machek
2004-08-11 1:02 ` [RFC] Fix Device Power Management States Benjamin Herrenschmidt
2004-08-10 19:41 ` David Brownell
2004-08-10 22:44 ` Patrick Mochel
2004-08-10 10:33 ` Matthew Garrett
2004-08-10 14:36 ` Patrick Mochel
2004-08-10 19:18 ` David Brownell
2004-08-10 20:50 ` Pavel Machek
2004-08-11 1:47 ` Todd Poynor
2004-08-12 22:03 ` Russell King
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=20040811091304.GD674@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
/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.