linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com,
	linux-mm@kvack.org, Borislav Petkov <bp@suse.de>,
	Dave Hansen <dave.hansen@intel.com>
Subject: Re: [-] drop_caches-add-some-documentation-and-info-messsge.patch removed from -mm tree
Date: Fri, 12 Jul 2013 13:50:28 +0200	[thread overview]
Message-ID: <20130712115028.GC15307@dhcp22.suse.cz> (raw)
In-Reply-To: <20130711145034.3ec774d0a44742cf5d8e1177@linux-foundation.org>

On Thu 11-07-13 14:50:34, Andrew Morton wrote:
> On Thu, 11 Jul 2013 09:36:44 +0200 Michal Hocko <mhocko@suse.cz> wrote:
> 
> > On Wed 10-07-13 13:25:03, Andrew Morton wrote:
> > [...]
> > > This patch was dropped because it has gone stale
> > 
> > Is there really a strong reason to not take this patch? 
> 
> I flushed out a whole bunch of MM patches which had been floating
> around in indecisive limbo.
> 
> I don't recall all the review issues surrounding this one.

Kosaki was concerned about annoying number of messages if somebody drops
caches too often (https://lkml.org/lkml/2010/9/20/450). As I noted in
the changelog
"
    Kosaki was worried about possible excessive logging when somebody drops
    caches too often (but then he claimed he didn't have a strong opinion on
    that) but I would say opposite.  If somebody does that then I would really
    like to know that from the log when supporting a system because it almost
    for sure means that there is something fishy going on.  It is also worth
    mentioning that only root can write drop caches so this is not an flooding
    attack vector.
"

Kosaki then Acked the patch.

You were worried (http://lkml.indiana.edu/hypermail/linux/kernel/1210.3/00605.html)
about people hating us because they are using this as a solution to
their issues. I concur that most of those are just hacks that found
their way into scripts looong time agon and stayed there.

Boris then noted (http://lkml.indiana.edu/hypermail/linux/kernel/1210.3/00659.html)
that he is using drop_caches to make s2ram faster but as others noted
this just adds the overhead to the resume path so it might work only for
certain use cases so a user space solution is more appropriate and
Boris' use case really sounds valid.

As a compromise I can lower the log level. Would KERN_INFO work for
you? Or even KERN_DEBUG?

I still find printk less intrusive than fiddling with vmstat counters.
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-07-12 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51ddc31f.zotz9WDKK3lWXtDE%akpm@linux-foundation.org>
2013-07-11  7:36 ` [-] drop_caches-add-some-documentation-and-info-messsge.patch removed from -mm tree Michal Hocko
2013-07-11 12:39   ` Michal Hocko
2013-07-11 15:34     ` Dave Hansen
2013-07-11 15:42       ` Michal Hocko
2013-07-11 15:45         ` Dave Hansen
2013-07-11 21:50   ` Andrew Morton
2013-07-12 11:50     ` Michal Hocko [this message]
2013-07-12 12:25       ` Borislav Petkov
2013-07-12 19:08       ` KOSAKI Motohiro

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=20130712115028.GC15307@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=dave.hansen@intel.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.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 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).