From: Bill Davidsen <davidsen@tmr.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Thaw userspace and kernel space separately.
Date: Sat, 28 Oct 2006 20:04:47 -0400 [thread overview]
Message-ID: <4543F01F.2010606@tmr.com> (raw)
In-Reply-To: <20061023151845.GB8414@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>> Modify process thawing so that we can thaw kernel space without thawing
>> userspace, and thaw kernelspace first. This will be useful in later
>> patches, where I intend to get swsusp thawing kernel threads only before
>> seeking to free memory.
>>
>> Signed-off-by: Nigel Cunningham <nigel@suspend2.net>
>
> NAK. "May be useful in future" is not good reason to merge it now. (If
> you did not want it merged, just mark it so).
I hope Nigel will keep working at it, since low memory machines like old
laptops would benefit from suspend are a reality. It can be kept as a
separate patch somewhere, like suspend2, which people can patch in to
enhance the example code currently in the kernel.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
prev parent reply other threads:[~2006-10-29 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 23:48 [PATCH] Thaw userspace and kernel space separately Nigel Cunningham
2006-10-23 10:26 ` Rafael J. Wysocki
2006-10-23 12:00 ` Nigel Cunningham
2006-10-23 13:41 ` Rafael J. Wysocki
2006-10-23 16:51 ` Andrew Morton
2006-10-23 18:37 ` Rafael J. Wysocki
2006-10-25 17:45 ` dean gaudet
2006-10-23 15:18 ` Pavel Machek
2006-10-29 0:04 ` Bill Davidsen [this message]
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=4543F01F.2010606@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox