linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Michal Hocko <mhocko@suse.cz>,
	linux-mm@kvack.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] add some drop_caches documentation and info messsge
Date: Mon, 29 Oct 2012 11:11:20 +0100	[thread overview]
Message-ID: <20121029101120.GC4326@liondog.tnic> (raw)
In-Reply-To: <alpine.LNX.2.00.1210291100470.19184@pobox.suse.cz>

On Mon, Oct 29, 2012 at 11:01:59AM +0100, Jiri Kosina wrote:
> Well if the point of dropping caches is lowering the resume time, then
> the point is rendered moot as soon as you switch to your browser and
> have to wait noticeable amount of time until it starts reacting.

Not the resume time - the suspend time. If, say, one has 8Gb of memory
and Linux nicely spreads all over it in caches, you don't want to wait
too long for the suspend image creation.

And nowadays, since you can have 8Gb in a laptop, you really want to
keep that image minimal so that suspend-to-disk is quick.

The penalty of faulting everything back in is a cost we'd be willing to
pay, I guess.

Thanks.

-- 
Regards/Gruss,
    Boris.

  reply	other threads:[~2012-10-29 10:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 12:57 [PATCH] add some drop_caches documentation and info messsge Michal Hocko
2012-10-12 18:54 ` KOSAKI Motohiro
2012-10-15  9:04 ` Kamezawa Hiroyuki
2012-10-15 14:05 ` Dave Hansen
2012-10-23 23:45 ` Andrew Morton
2012-10-24  6:29   ` Michal Hocko
2012-10-24 19:54     ` Andrew Morton
2012-10-24 20:28       ` Dave Hansen
2012-10-24 20:48         ` Andrew Morton
2012-10-24 21:06           ` Borislav Petkov
2012-10-24 21:13             ` Andrew Morton
2012-10-24 22:04               ` Rafael J. Wysocki
2012-10-25  1:17                 ` Andrew Morton
2012-10-25 20:16                   ` Rafael J. Wysocki
2012-10-29  8:59                   ` Jiri Kosina
2012-10-29  9:58                     ` Borislav Petkov
2012-10-29 10:01                       ` Jiri Kosina
2012-10-29 10:11                         ` Borislav Petkov [this message]
2012-10-31 17:31                       ` Pavel Machek
2012-10-31 17:46                         ` Borislav Petkov
2012-10-24 22:35               ` KOSAKI Motohiro
2012-10-25 14:21                 ` Michal Hocko
2012-10-24 21:18             ` Dave Hansen
2012-10-24 22:48               ` Borislav Petkov
2012-10-24 22:57                 ` Dave Hansen
2012-10-25  0:56                   ` KOSAKI Motohiro
2012-10-25  9:24                     ` Borislav Petkov
2012-10-25 11:57                       ` Dave Hansen
2012-10-25 14:24                         ` Borislav Petkov
2012-10-25 14:25                         ` Michal Hocko
2012-10-26  7:45           ` Mika Boström
2012-11-01 20:26           ` Pavel Machek
2012-10-25 14:09       ` Michal Hocko

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=20121029101120.GC4326@liondog.tnic \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=jkosina@suse.cz \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.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;
as well as URLs for NNTP newsgroup(s).