Message-ID: <51FBE807.6040907@intel.com>
Date: Fri, 02 Aug 2013 10:10:31 -0700
From: Dave Hansen <dave.hansen@intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
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
References: <1375459442.8422.1@driftwood>
In-Reply-To: <1375459442.8422.1@driftwood>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1171
Lines: 23

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/