public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux PM <linux-pm@osdl.org>
Subject: Re: [RFC/RFT][PATCH 2/2] swsusp: improve freeing of memory
Date: Thu, 10 Nov 2005 11:12:46 +0100	[thread overview]
Message-ID: <200511101112.47139.rjw@sisk.pl> (raw)
In-Reply-To: <20051109231544.GI12459@elf.ucw.cz>

Hi,

On Thursday, 10 of November 2005 00:15, Pavel Machek wrote:
> Hi!
> 
> > > For console users, it may be preferable... 
> > 
> > Well, that depends on what the user is doing in general, but do you have
> > any specific scenario in mind?
> 
> Well, when I'm working on console, little latency does not hurt. I
> can't work at all while system is reading image, but I can work quite
> well while system is swapping in... on the console, that is.

OK, so do you want a kconfig option for switching on the "free as much
memory as you can" behavior then?

Rafael

  reply	other threads:[~2005-11-10 10:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 22:55 [RFC/RFT][PATCH 0/2] swsusp: improve freeing of memory Rafael J. Wysocki
2005-11-08 23:06 ` [RFC/RFT][PATCH 1/2] swsusp: introduce the swap map structure Rafael J. Wysocki
2005-11-08 23:11 ` [RFC/RFT][PATCH 2/2] swsusp: improve freeing of memory Rafael J. Wysocki
2005-11-09 14:46   ` Pavel Machek
2005-11-09 22:38     ` Rafael J. Wysocki
2005-11-09 23:15       ` Pavel Machek
2005-11-10 10:12         ` Rafael J. Wysocki [this message]
2005-11-09  0:32 ` [RFC/RFT][PATCH 0/2] " Pavel Machek
2005-11-09 22:49   ` Rafael J. Wysocki
2005-11-09 23:19     ` Pavel Machek
2005-11-10 10:34       ` Rafael J. Wysocki
2005-11-10 10:48         ` Pavel Machek
2005-11-09 14:30 ` Pavel Machek
2005-11-09 21:04   ` Pavel Machek
2005-11-09 23:07     ` Rafael J. Wysocki
2005-11-09 22:55   ` Rafael J. Wysocki
2005-11-09 23:22     ` Pavel Machek

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=200511101112.47139.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox