From: Johannes Weiner <hannes@cmpxchg.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>,
lizefan@huawei.com, axboe@kernel.dk, dennis@kernel.org,
Dennis Zhou <dennisszhou@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
cgroups@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kernel-team@android.com
Subject: Re: [PATCH 6/6] psi: introduce psi monitor
Date: Tue, 18 Dec 2018 12:30:00 -0500 [thread overview]
Message-ID: <20181218173000.GA4733@cmpxchg.org> (raw)
In-Reply-To: <20181218104622.GB15430@hirez.programming.kicks-ass.net>
On Tue, Dec 18, 2018 at 11:46:22AM +0100, Peter Zijlstra wrote:
> On Mon, Dec 17, 2018 at 05:21:05PM -0800, Suren Baghdasaryan wrote:
> > On Mon, Dec 17, 2018 at 8:22 AM Peter Zijlstra <peterz@infradead.org> wrote:
>
> > > How well has this thing been fuzzed? Custom string parser, yay!
> >
> > Honestly, not much. Normal cases and some obvious corner cases. Will
> > check if I can use some fuzzer to get more coverage or will write a
> > script.
> > I'm not thrilled about writing a custom parser, so if there is a
> > better way to handle this please advise.
>
> The grammar seems fairly simple, something like:
>
> some-full = "some" | "full" ;
> threshold-abs = integer ;
> threshold-pct = integer, { "%" } ;
> threshold = threshold-abs | threshold-pct ;
> window = integer ;
> trigger = some-full, space, threshold, space, window ;
>
> And that could even be expressed as two scanf formats:
>
> "%4s %u%% %u" , "%4s %u %u"
>
> which then gets your something like:
>
> char type[5];
>
> if (sscanf(input, "%4s %u%% %u", &type, &pct, &window) == 3) {
> // do pct thing
> } else if (sscanf(intput, "%4s %u %u", &type, &thres, &window) == 3) {
> // do abs thing
> } else return -EFAIL;
>
> if (!strcmp(type, "some")) {
> // some
> } else if (!strcmp(type, "full")) {
> // full
> } else return -EFAIL;
>
> // do more
We might want to drop the percentage notation.
While it's somewhat convenient, it's also not unreasonable to ask
userspace to do a simple "threshold * win / 100" themselves, and it
would simplify the interface spec and the parser.
Sure, psi outputs percentages, but only for fixed window sizes, so
that actually saves us something, whereas this parser here needs to
take a fractional anyway. The output is also in decimal notation,
which is necessary for granularity. And I really don't think we want
to add float parsing on top of this interface spec.
So neither the convenience nor the symmetry argument are very
compelling IMO. It might be better to just not go there.
next prev parent reply other threads:[~2018-12-18 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:15 [PATCH 0/6] psi: pressure stall monitors Suren Baghdasaryan
2018-12-14 17:15 ` [PATCH 1/6] fs: kernfs: add poll file operation Suren Baghdasaryan
2018-12-14 17:15 ` [PATCH 2/6] kernel: cgroup: " Suren Baghdasaryan
2018-12-14 17:15 ` [PATCH 3/6] psi: eliminate lazy clock mode Suren Baghdasaryan
2018-12-17 14:57 ` Peter Zijlstra
2018-12-18 1:10 ` Suren Baghdasaryan
2018-12-14 17:15 ` [PATCH 4/6] psi: introduce state_mask to represent stalled psi states Suren Baghdasaryan
2018-12-17 15:55 ` Peter Zijlstra
2018-12-18 1:14 ` Suren Baghdasaryan
2018-12-18 10:17 ` Peter Zijlstra
2018-12-14 17:15 ` [PATCH 5/6] psi: rename psi fields in preparation for psi trigger addition Suren Baghdasaryan
2018-12-14 17:15 ` [PATCH 6/6] psi: introduce psi monitor Suren Baghdasaryan
2018-12-17 16:22 ` Peter Zijlstra
2018-12-18 1:21 ` Suren Baghdasaryan
2018-12-18 10:46 ` Peter Zijlstra
2018-12-18 11:20 ` Peter Zijlstra
2018-12-18 17:30 ` Johannes Weiner [this message]
2018-12-18 17:58 ` Suren Baghdasaryan
2018-12-18 19:18 ` Joel Fernandes
2018-12-18 20:29 ` Suren Baghdasaryan
2018-12-17 16:27 ` Peter Zijlstra
2018-12-18 1:22 ` Suren Baghdasaryan
2018-12-18 16:51 ` kbuild test robot
2018-12-22 14:12 ` kbuild test robot
2018-12-22 14:12 ` kbuild test robot
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=20181218173000.GA4733@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dennis@kernel.org \
--cc=dennisszhou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=surenb@google.com \
--cc=tj@kernel.org \
/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