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: Tue, 11 Feb 2014 13:44:59 -0800 [thread overview]
Message-ID: <20140211134459.551dd07d697a888e29f1c7b1@linux-foundation.org> (raw)
In-Reply-To: <20140210215416.GK6963@cmpxchg.org>
On Mon, 10 Feb 2014 16:54:16 -0500 Johannes Weiner <hannes@cmpxchg.org> wrote:
> How about this: we allow disabling the log message, but print the line
> of the disabling call so it's clear who dunnit. To make sure valuable
> info is not missing in bug reports, add counters for the two events in
> /proc/vmstat.
>
> Does that sound acceptable?
Yes, I really don't know what's the right thing to do here or where the
best tradeoff point is situated. Let's start off this way and see what
happens I guess.
> --- a/fs/drop_caches.c
> +++ b/fs/drop_caches.c
> @@ -59,10 +59,22 @@ int drop_caches_sysctl_handler(ctl_table *table, int write,
> if (ret)
> return ret;
> if (write) {
> - if (sysctl_drop_caches & 1)
> + static int stfu;
That identifier wasn't serious, but I kinda like it.
> +
> + if (sysctl_drop_caches & 1) {
> iterate_supers(drop_pagecache_sb, NULL);
> - if (sysctl_drop_caches & 2)
> + count_vm_event(DROP_PAGECACHE);
> + }
> + if (sysctl_drop_caches & 2) {
> drop_slab();
> + count_vm_event(DROP_SLAB);
> + }
> + if (!stfu) {
> + pr_info("%s (%d): drop_caches: %d\n",
> + current->comm, task_pid_nr(current),
> + sysctl_drop_caches);
> + }
> + stfu |= sysctl_drop_caches & 4;
> }
> return 0;
> }
--
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-11 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 17:40 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
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 [this message]
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=20140211134459.551dd07d697a888e29f1c7b1@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