From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath: DFS - limit number of potential PRI sequences
Date: Tue, 30 Jun 2015 15:34:34 +0300 [thread overview]
Message-ID: <87si991ijp.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1434443643-28477-1-git-send-email-zefir.kurtisi@neratec.com> (Zefir Kurtisi's message of "Tue, 16 Jun 2015 10:34:03 +0200")
Zefir Kurtisi <zefir.kurtisi@neratec.com> writes:
> In the PRI detector, after the current radar pulse
> has been checked agains existing PRI sequences, it
> is considered as part of a new potential sequence.
>
> Previously, the condition to accept a new sequence
> was to have at least the same number of pulses as
> the longest matching sequence. This was wrong,
> since it led to duplicates of PRI sequences.
>
> This patch changes the acceptance criteria for new
> potential sequences from 'at least' to 'more than'
> the longest existing.
>
> Detection performance remains unaffected, while
> the number of PRI sequences accounted at runtime
> (and with it CPU load) is reduced by up to 50%.
>
> Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Thanks, applied to ath.git.
--
Kalle Valo
prev parent reply other threads:[~2015-06-30 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 8:34 [ath9k-devel] [PATCH] ath: DFS - limit number of potential PRI sequences Zefir Kurtisi
2015-06-30 12:34 ` Kalle Valo [this message]
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=87si991ijp.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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