From: Steven Rostedt <rostedt@goodmis.org>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: surenb@google.com, hridya@google.com, namhyung@kernel.org,
kernel-team@android.com, Jonathan Corbet <corbet@lwn.net>,
Ingo Molnar <mingo@redhat.com>, Shuah Khan <shuah@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <zanussi@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 2/5] tracing: Add division and multiplication support for hist triggers
Date: Tue, 19 Oct 2021 22:27:56 -0400 [thread overview]
Message-ID: <20211019222756.1fde436b@gandalf.local.home> (raw)
In-Reply-To: <20211020013153.4106001-3-kaleshsingh@google.com>
On Tue, 19 Oct 2021 18:31:39 -0700
Kalesh Singh <kaleshsingh@google.com> wrote:
> +static u64 hist_field_div(struct hist_field *hist_field,
> + struct tracing_map_elt *elt,
> + struct trace_buffer *buffer,
> + struct ring_buffer_event *rbe,
> + void *event)
> +{
> + struct hist_field *operand1 = hist_field->operands[0];
> + struct hist_field *operand2 = hist_field->operands[1];
> +
> + u64 val1 = operand1->fn(operand1, elt, buffer, rbe, event);
> + u64 val2 = operand2->fn(operand2, elt, buffer, rbe, event);
> +
> + /* Return -1 for the undefined case */
> + if (!val2)
> + return -1;
> +
> + return div64_u64(val1, val2);
> +}
> +
I wonder if you should add a shift operator as well?
I mean, if for some reason you want to divide by a power of two, then why
us the division. Especially if this is on a 32 bit machine.
Of course, the parsing could detect that. If the divisor is a constant. Or
we could even optimize the above with:
if (!val2)
return -1;
if (!(val2 & (val2 - 1))
return val1 >> __ffs64(val2);
Which should be faster than a divide, and even if it isn't a power of two,
the subtract and & should be in the noise compared to the divide.
Note, the above can be added to this. I'm not suggesting changing this
patch.
-- Steve
next prev parent reply other threads:[~2021-10-20 2:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 1:31 [PATCH v2 0/5] tracing: Extend histogram triggers expression parsing Kalesh Singh
2021-10-20 1:31 ` [PATCH v2 1/5] tracing: Add support for creating hist trigger variables from literal Kalesh Singh
2021-10-20 15:32 ` Steven Rostedt
2021-10-20 15:55 ` Kalesh Singh
2021-10-20 15:59 ` Steven Rostedt
2021-10-20 1:31 ` [PATCH v2 2/5] tracing: Add division and multiplication support for hist triggers Kalesh Singh
2021-10-20 2:27 ` Steven Rostedt [this message]
2021-10-20 14:54 ` Kalesh Singh
2021-10-20 15:13 ` Steven Rostedt
2021-10-20 15:23 ` Kalesh Singh
2021-10-20 1:31 ` [PATCH v2 3/5] tracing: Fix operator precedence for hist triggers expression Kalesh Singh
2021-10-20 14:28 ` Steven Rostedt
2021-10-20 15:06 ` Kalesh Singh
2021-10-20 15:13 ` Steven Rostedt
2021-10-20 15:48 ` Steven Rostedt
2021-10-20 16:11 ` Kalesh Singh
2021-10-20 16:19 ` Steven Rostedt
2021-10-20 16:22 ` Kalesh Singh
2021-10-20 1:31 ` [PATCH v2 4/5] tracing/selftests: Add tests for hist trigger expression parsing Kalesh Singh
2021-10-20 1:31 ` [PATCH v2 5/5] tracing/histogram: Document expression arithmetic and constants Kalesh Singh
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=20211019222756.1fde436b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=hridya@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=zanussi@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
all inboxes | Powered by JetHome®