From: Kevin Fang <chienf@qca.qualcomm.com>
To: <kvalo@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: [PATCH 2/2] ath6kl: assign Tx packet drop threshold per endpoint on htc pipe layer
Date: Fri, 27 Apr 2012 09:18:02 +0800 [thread overview]
Message-ID: <1335489482-15565-2-git-send-email-kevin.fang@qca.qualcomm.com> (raw)
In-Reply-To: <1335489482-15565-1-git-send-email-kevin.fang@qca.qualcomm.com>
on the htc mbox layer, it will assign each endpoint (AC)
with a different Tx-packet-drop threshold,
so lower priority AC is more likely to drop packets
and the cookies become more available to higher priority AC.
on the htc pipe layer, assign the tx packet drop threshold as well,
it will let AC to drop packets when cookies below the tx packet drop thresho
Signed-off-by: Kevin Fang <kevin.fang@qca.qualcomm.com>
---
drivers/net/wireless/ath/ath6kl/htc_pipe.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath6kl/htc_pipe.c b/drivers/net/wireless/ath/ath6kl/htc_pipe.c
index b21a69f..f9626c7 100644
--- a/drivers/net/wireless/ath/ath6kl/htc_pipe.c
+++ b/drivers/net/wireless/ath/ath6kl/htc_pipe.c
@@ -1378,6 +1378,9 @@ static int ath6kl_htc_pipe_conn_service(struct htc_target *target,
/* copy all the callbacks */
ep->ep_cb = conn_req->ep_cb;
+ /* initialize tx_drop_packet_threshold */
+ ep->tx_drop_packet_threshold = MAX_HI_COOKIE_NUM;
+
status = ath6kl_hif_pipe_map_service(ar, ep->svc_id,
&ep->pipe.pipeid_ul,
&ep->pipe.pipeid_dl);
--
1.7.0.4
next prev parent reply other threads:[~2012-04-27 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 1:18 [PATCH 1/2] ath6kl: handle background(BK) stream properly on htc mbox layer Kevin Fang
2012-04-27 1:18 ` Kevin Fang [this message]
2012-04-27 7:00 ` Kalle Valo
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=1335489482-15565-2-git-send-email-kevin.fang@qca.qualcomm.com \
--to=chienf@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).