From: Dave Hansen <dave.hansen@intel.com>
To: Rob Landley <rob@landley.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
mhocko@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kamezawa.hiroyu@jp.fujitsu.com, bp@suse.de,
dave@linux.vnet.ibm.com
Subject: Re: [PATCH resend] drop_caches: add some documentation and info message
Date: Fri, 02 Aug 2013 10:10:31 -0700 [thread overview]
Message-ID: <51FBE807.6040907@intel.com> (raw)
In-Reply-To: <1375459442.8422.1@driftwood>
On 08/02/2013 09:04 AM, Rob Landley wrote:
> I'd be surprised if anybody who does this sees the printk and thinks
> "hey, I'll dig into the VM's balancing logic and come up to speed on the
> tradeoffs sufficient to contribute to kernel development" because of
> something in dmesg. Anybody actually annoyed by it will chop out the
> printk (you barely need to know C to do that), the rest won't notice.
All that I expect is that this will get _some_ of these folks in to a
feedback loop with us. They'll see this in dmesg and either go asking
questions within their respective companies, file bugs with distros, or
post to LKML.
Some of them are going to say things like "My Database Vendor told me
this optimizes my server!", or that the documentation told them to do it
so they don't run out of memory. Some of them might even be running in
to _legitimate_ VM or filesystem bugs that they're working around with this.
--
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>
prev parent reply other threads:[~2013-08-02 17:10 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
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 [this message]
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=51FBE807.6040907@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--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 \
--cc=mhocko@suse.cz \
--cc=rob@landley.net \
/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).