All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Add probe response throttling logic
Date: Wed, 17 Jul 2019 12:21:54 +0000 (UTC)	[thread overview]
Message-ID: <20190717122154.8107F611CF@smtp.codeaurora.org> (raw)
In-Reply-To: <1561595753-11351-1-git-send-email-srirrama@codeaurora.org>

Sriram R <srirrama@codeaurora.org> wrote:

> Drop probe response packets when the pending management tx
> count has reached a certain threshold, so as to prioritize
> other mgmt packets like auth and assoc to be sent on time
> for establishing successful connections.
> This might be required in dense networks, multi-vap scenarios
> or due to emulated probe requests (DoS attack),
> which could lead to association failures due to failure to
> send auth/assoc packets as high probe response traffic occupies the
> limited target mgmt transmit queue.
> Currently the threshold is set to 3/4th of the target management
> tx queue.
> 
> Signed-off-by: Sriram R <srirrama@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath11k-bringup branch of ath.git, thanks.

1a50014ff2d3 ath11k: Add probe response throttling logic

-- 
https://patchwork.kernel.org/patch/11018825/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      parent reply	other threads:[~2019-07-17 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  0:35 [PATCH] ath11k: Add probe response throttling logic Sriram R
2019-07-16 12:13 ` Kalle Valo
2019-07-16 14:43   ` Sriram R
2019-07-17 12:21 ` 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=20190717122154.8107F611CF@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=srirrama@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.