From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: frank0988 <frank0988855428@gmail.com>,
Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: ath: avoid repeated divisions in DFS PRI detector
Date: Wed, 1 Jul 2026 12:08:34 -0700 [thread overview]
Message-ID: <079f2b0f-87f5-40bf-b36e-3ed01592e937@oss.qualcomm.com> (raw)
In-Reply-To: <20260701170424.380202-1-frank0988855428@gmail.com>
On 7/1/2026 10:04 AM, frank0988 wrote:
> pde_get_multiple() is called repeatedly with the same PRI (Pulse
> Repetition Interval) value while validating candidate and existing PRI
> sequences.
>
> Cache the reciprocal value for each sequence structure and leverage
> reciprocal_divide() in the hot path. This keeps the existing matching
> logic and tolerance checks intact while replacing expensive hardware
> integer divisions with low-cost multiply-and-shift operations.
>
> Testing with a userspace model of the same detector logic demonstrated
> identical detector states and outputs across 100 verification traces.
> To eliminate memory allocator noise, an isolated micro-benchmark using
> a static object pool showed that the reciprocal variant reduces CPU
> cycles by approximately 3.4%.
>
> Signed-off-by: frank0988 <frank0988855428@gmail.com>
You must sign off with a "known identity"
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#developer-s-certificate-of-origin-1-1
next prev parent reply other threads:[~2026-07-01 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 17:04 [PATCH] wifi: ath: avoid repeated divisions in DFS PRI detector frank0988
2026-07-01 19:08 ` Jeff Johnson [this message]
2026-07-02 3:52 ` [PATCH v2] " Chun-Cheng Chang
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=079f2b0f-87f5-40bf-b36e-3ed01592e937@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=frank0988855428@gmail.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.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