From: Dave Chinner <david@fromorbit.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Thomas Knauth <thomas.knauth@gmx.de>,
David Rientjes <rientjes@google.com>,
Maksym Planeta <mcsim.planeta@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl: Add a feature to drop caches selectively
Date: Fri, 27 Jun 2014 12:48:34 +1000 [thread overview]
Message-ID: <20140627024834.GX9508@dastard> (raw)
In-Reply-To: <1403763199.20275.39.camel@sauron.fi.intel.com>
On Thu, Jun 26, 2014 at 09:13:19AM +0300, Artem Bityutskiy wrote:
> 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?
Just add the dev/mntpt to /etc/fstab and add "user" to the
configuration and the need for root goes away.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-06-27 2:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 16:10 [PATCH] sysctl: Add a feature to drop caches selectively Maksym Planeta
2014-06-24 21:59 ` David Rientjes
2014-06-25 6:25 ` Artem Bityutskiy
2014-06-25 8:25 ` Thomas Knauth
2014-06-25 9:56 ` Artem Bityutskiy
2014-06-25 13:23 ` Thomas Knauth
2014-06-25 13:30 ` Artem Bityutskiy
2014-06-25 13:42 ` Artem Bityutskiy
2014-06-26 9:30 ` Maksym Planeta
2014-06-25 10:03 ` Artem Bityutskiy
2014-06-25 13:19 ` Thomas Knauth
2014-06-25 22:15 ` Pavel Machek
2014-06-26 1:06 ` Dave Chinner
2014-06-26 6:13 ` Artem Bityutskiy
2014-06-26 10:36 ` Bernd Schubert
2014-06-26 11:31 ` Artem Bityutskiy
2014-06-26 11:57 ` Lukáš Czerner
2014-06-26 12:10 ` Bernd Schubert
2014-06-27 2:55 ` Dave Chinner
2014-06-27 8:58 ` Bernd Schubert
2014-06-27 8:41 ` Matthias Schniedermeyer
2014-06-27 9:04 ` Lukáš Czerner
2014-06-27 9:08 ` Artem Bityutskiy
2014-06-27 9:09 ` Bityutskiy, Artem
2014-06-27 2:48 ` Dave Chinner [this message]
[not found] <CACVxJT_6sp=KDy=jCNBypYapKv_59W8LxFU4OiJEm6gt_SuZKg@mail.gmail.com>
2014-06-25 11:21 ` Alexey Dobriyan
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=20140627024834.GX9508@dastard \
--to=david@fromorbit.com \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcsim.planeta@gmail.com \
--cc=rientjes@google.com \
--cc=thomas.knauth@gmx.de \
--cc=viro@zeniv.linux.org.uk \
/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