From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Manikanta Pubbisetty <mpubbise@codeaurora.org>,
johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
Manikanta Pubbisetty <mpubbise@codeaurora.org>
Subject: Re: [PATCH] mac80211: add stop/start logic for software TXQs
Date: Tue, 26 Jun 2018 13:25:46 +0200 [thread overview]
Message-ID: <878t71n611.fsf@toke.dk> (raw)
In-Reply-To: <1529997415-20551-1-git-send-email-mpubbise@codeaurora.org>
Manikanta Pubbisetty <mpubbise@codeaurora.org> writes:
> We can still invoke netif stop/wake APIs when wake_tx_queue is
> implemented but this could lead to packet drops in network layer;
> adding stop/start logic for software TXQs in mac80211 instead makes
> more sense; the change proposed adds the same in mac80211.
I agree with the approach; having packets queued in mac80211 while the
queues are stopped also means that CoDel can react to them when they are
resumed again.
> + list_for_each_entry_rcu(sta, &local->sta_list, list) {
> + if (!atomic_read(&sta->txqs_paused))
> + continue;
> +
> + atomic_set(&sta->txqs_paused, 0);
I'm not terribly well-versed in the kernel atomics, but doesn't the
split of read and set kinda defeat the point of using them? Also, as
this is under RCU, why do you need an atomic in the first place?
-Toke
next prev parent reply other threads:[~2018-06-26 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 7:16 [PATCH] mac80211: add stop/start logic for software TXQs Manikanta Pubbisetty
2018-06-26 11:25 ` Toke Høiland-Jørgensen [this message]
2018-06-26 12:31 ` Manikanta Pubbisetty
2018-06-27 12:28 ` Toke Høiland-Jørgensen
2018-06-29 7:58 ` Johannes Berg
2018-06-29 7:57 ` Johannes Berg
2018-07-02 9:34 ` Manikanta Pubbisetty
2018-06-26 11:27 ` kbuild test robot
2018-06-29 9:09 ` Johannes Berg
2018-07-02 9:18 ` Manikanta Pubbisetty
2018-07-03 9:45 ` Johannes Berg
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=878t71n611.fsf@toke.dk \
--to=toke@toke.dk \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@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.