From mboxrd@z Thu Jan 1 00:00:00 1970 From: Artem Bityutskiy Subject: Re: [PATCH] sysctl: Add a feature to drop caches selectively Date: Thu, 26 Jun 2014 09:13:19 +0300 Message-ID: <1403763199.20275.39.camel@sauron.fi.intel.com> References: <1403626213-7691-1-git-send-email-mcsim.planeta@gmail.com> <1403677528.7903.103.camel@sauron.fi.intel.com> <20140626010606.GT4453@dastard> Reply-To: dedekind1@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Thomas Knauth , David Rientjes , Maksym Planeta , Alexander Viro , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Dave Chinner Return-path: In-Reply-To: <20140626010606.GT4453@dastard> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2014-06-26 at 11:06 +1000, Dave Chinner wrote: > Your particular use case can be handled by directing your benchmark > at a filesystem mount point and unmounting the filesystem in between > benchmark runs. There is no ned to adding kernel functionality for > somethign that can be so easily acheived by other means, especially > in benchmark environments where *everything* is tightly controlled. If I was a benchmark writer, I would not be willing running it as root to be able to mount/unmount, I would not be willing to require the customer creating special dedicated partitions for the benchmark, because this is too user-unfriendly. Or do I make incorrect assumptions? Not that I need this syscall and trying to sell the idea to anyone, just trying to understand the alternative you suggested. -- Best Regards, Artem Bityutskiy