linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	dave.hansen@intel.com,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	bp@suse.de, Dave Hansen <dave@linux.vnet.ibm.com>
Subject: Re: [PATCH resend] drop_caches: add some documentation and info message
Date: Fri, 2 Aug 2013 09:33:04 +0200	[thread overview]
Message-ID: <20130802073304.GA17746@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHGf_=r7mek+ueJWfu_6giMOueDTnMs8dY1jJrKyX+gfPys6uA@mail.gmail.com>

On Thu 01-08-13 21:39:48, KOSAKI Motohiro wrote:
> On Wed, Jul 31, 2013 at 11:17 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > On Wed, 31 Jul 2013 23:11:50 -0400 KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> >
> >> >> --- a/fs/drop_caches.c
> >> >> +++ b/fs/drop_caches.c
> >> >> @@ -59,6 +59,8 @@ int drop_caches_sysctl_handler(ctl_table *table, int write,
> >> >>    if (ret)
> >> >>            return ret;
> >> >>    if (write) {
> >> >> +          printk(KERN_INFO "%s (%d): dropped kernel caches: %d\n",
> >> >> +                 current->comm, task_pid_nr(current), sysctl_drop_caches);
> >> >>            if (sysctl_drop_caches & 1)
> >> >>                    iterate_supers(drop_pagecache_sb, NULL);
> >> >>            if (sysctl_drop_caches & 2)
> >> >
> >> > How about we do
> >> >
> >> >     if (!(sysctl_drop_caches & 4))
> >> >             printk(....)
> >> >
> >> > so people can turn it off if it's causing problems?
> >>
> >> The best interface depends on the purpose. If you want to detect crazy application,
> >> we can't assume an application co-operate us. So, I doubt this works.
> >
> > You missed the "!".  I'm proposing that setting the new bit 2 will
> > permit people to prevent the new printk if it is causing them problems.
> 
> No I don't. I'm sure almost all abuse users think our usage is correct. Then,
> I can imagine all crazy applications start to use this flag eventually.

I guess we do not care about those. If somebody wants to shoot his feet
then we cannot do much about it. The primary motivation was to find out
those that think this is right and they are willing to change the setup
once they know this is not the right way to do things.

I think that giving a way to suppress the warning is a good step. Log
level might be to coarse and sysctl would be an overkill.

-- 
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-08-02  7:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 12:44 [PATCH resend] drop_caches: add some documentation and info message Michal Hocko
2013-07-26 21:37 ` Johannes Weiner
2013-07-29 20:57 ` Andrew Morton
2013-07-30  7:45   ` Michal Hocko
2013-07-30  8:25     ` Andrew Morton
2013-07-30 12:55       ` Michal Hocko
2013-07-30 14:39         ` Andrew Morton
2013-07-30 14:47           ` Michal Hocko
2013-07-30 14:47         ` Dave Hansen
2013-07-30 14:54           ` Borislav Petkov
2013-07-30 15:08           ` Andrew Morton
2013-08-01  3:11   ` KOSAKI Motohiro
2013-08-01  3:17     ` Andrew Morton
2013-08-02  1:39       ` KOSAKI Motohiro
2013-08-02  7:33         ` Michal Hocko [this message]
2013-08-03 20:16           ` KOSAKI Motohiro
2013-08-04  8:07             ` Michal Hocko
2013-08-05  1:13               ` KOSAKI Motohiro
2013-08-05  7:20                 ` Michal Hocko
2013-09-17 15:14                   ` Johannes Weiner
2013-08-02 16:04       ` Rob Landley
2013-08-02 17:10         ` Dave Hansen

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=20130802073304.GA17746@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=dave.hansen@intel.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).