From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Rik van Riel <riel@redhat.com>, Dave Hansen <dave@sr71.net>,
Michal Hocko <mhocko@suse.cz>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] drop_caches: add some documentation and info message
Date: Fri, 7 Feb 2014 12:31:29 -0800 [thread overview]
Message-ID: <20140207123129.84f9fb0aaf32f0e09c78851a@linux-foundation.org> (raw)
In-Reply-To: <20140207181332.GG6963@cmpxchg.org>
On Fri, 7 Feb 2014 13:13:32 -0500 Johannes Weiner <hannes@cmpxchg.org> wrote:
> @@ -63,6 +64,9 @@ int drop_caches_sysctl_handler(ctl_table *table, int write,
> iterate_supers(drop_pagecache_sb, NULL);
> if (sysctl_drop_caches & 2)
> drop_slab();
> + printk_ratelimited(KERN_INFO "%s (%d): dropped kernel caches: %d\n",
> + current->comm, task_pid_nr(current),
> + sysctl_drop_caches);
> }
> return 0;
> }
My concern with this is that there may be people whose
other-party-provided software uses drop_caches. Their machines will
now sit there emitting log messages and there's nothing they can do
about it, apart from whining at their vendors.
We could do something like this?
--- a/fs/drop_caches.c~drop_caches-add-some-documentation-and-info-message-fix
+++ a/fs/drop_caches.c
@@ -60,13 +60,17 @@ int drop_caches_sysctl_handler(ctl_table
if (ret)
return ret;
if (write) {
+ static int stfu;
+
if (sysctl_drop_caches & 1)
iterate_supers(drop_pagecache_sb, NULL);
if (sysctl_drop_caches & 2)
drop_slab();
- printk_ratelimited(KERN_INFO "%s (%d): dropped kernel caches: %d\n",
- current->comm, task_pid_nr(current),
- sysctl_drop_caches);
+ stfu |= sysctl_drop_caches & 4;
+ if (!stfu)
+ pr_info_ratelimited("%s (%d): dropped kernel caches: %d\n",
+ current->comm, task_pid_nr(current),
+ sysctl_drop_caches);
}
return 0;
}
_
(note switch to pr_info_ratelimited)
--
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>
next prev parent reply other threads:[~2014-02-07 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 17:40 [patch] drop_caches: add some documentation and info message Johannes Weiner
2014-02-07 17:55 ` Rik van Riel
2014-02-07 18:13 ` Johannes Weiner
2014-02-07 19:29 ` Rik van Riel
2014-02-07 20:31 ` Andrew Morton [this message]
2014-02-07 21:26 ` Johannes Weiner
2014-02-10 20:51 ` Andrew Morton
2014-02-10 21:11 ` Motohiro Kosaki
2014-02-10 21:54 ` Johannes Weiner
2014-02-11 21:44 ` Andrew Morton
2014-02-08 11:55 ` Rafael Aquini
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=20140207123129.84f9fb0aaf32f0e09c78851a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=hannes@cmpxchg.org \
--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=riel@redhat.com \
/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).