From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] tracing: Add disable-filter-buf option
Date: Fri, 15 Dec 2023 12:24:14 -0500 [thread overview]
Message-ID: <fbf8991a-ce83-462c-b87a-b60c6635d223@efficios.com> (raw)
In-Reply-To: <20231215120417.567d5ea4@rorschach.local.home>
On 2023-12-15 12:04, Steven Rostedt wrote:
> On Fri, 15 Dec 2023 10:53:39 -0500
> Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
[...]
>>
>> So rather than stacking tons of "on/off" switches for filter
>> features, how about you let users express the mechanism they
>> want to use for filtering with a string instead ? e.g.
>>
>> filter-method="temp-buffer"
>> filter-method="ring-buffer"
>> filter-method="input-arguments"
>
> If I add other ways to filter, it will be a separate file to control
> that, but all options are on/off switches. Even if I add other
> functionality to the way buffers are created, this will still have the
> same functionality to turn the entire thing on or off.
I'll be clearer then: I think this is a bad ABI. In your reply, you justify
this bad ABI by implementation motivations.
I don't care about the implementation, I care about the ABI, and
I feel that your reply is not addressing my concern at all.
Moreover, double-negative boolean options (disable-X=false) are confusing.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2023-12-15 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 15:26 [PATCH] tracing: Add disable-filter-buf option Steven Rostedt
2023-12-15 15:53 ` Mathieu Desnoyers
2023-12-15 17:04 ` Steven Rostedt
2023-12-15 17:24 ` Mathieu Desnoyers [this message]
2023-12-15 17:34 ` Steven Rostedt
2023-12-15 18:25 ` Mathieu Desnoyers
2023-12-15 18:43 ` Steven Rostedt
2023-12-15 19:08 ` Mathieu Desnoyers
2023-12-17 8:10 ` Masami Hiramatsu
2023-12-17 23:56 ` Steven Rostedt
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=fbf8991a-ce83-462c-b87a-b60c6635d223@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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