From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Manikanta Pubbisetty <mpubbise@codeaurora.org>,
johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCHv2] mac80211: add stop/start logic for software TXQs
Date: Tue, 10 Jul 2018 19:39:37 +0200 [thread overview]
Message-ID: <87fu0rc7mu.fsf@toke.dk> (raw)
In-Reply-To: <b91ace0b-412a-c654-0a03-49ed7138abd0@codeaurora.org>
Manikanta Pubbisetty <mpubbise@codeaurora.org> writes:
> On 7/10/2018 8:52 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
>> Manikanta Pubbisetty <mpubbise@codeaurora.org> writes:
>>
>>> On 7/10/2018 6:28 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
>>>
>>>>> diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h
>>>>> index 172aeae..d07f7f9 100644
>>>>> --- a/net/mac80211/ieee80211_i.h
>>>>> +++ b/net/mac80211/ieee80211_i.h
>>>>> @@ -818,6 +818,7 @@ enum txq_info_flags {
>>>>> IEEE80211_TXQ_STOP,
>>>>> IEEE80211_TXQ_AMPDU,
>>>>> IEEE80211_TXQ_NO_AMSDU,
>>>>> + IEEE80211_TXQ_PAUSED,
>>>>> };
>>>> I think it would be a good idea to either rename the flags, or at least
>>>> add an explanation somewhere of the difference between a paused and a
>>>> stopped queue...
>>> Initially, the idea was to use IEEE80211_TXQ_STOP flag to indicate that
>>> iTXQs are stopped; since this flag was used in the aggregation code, I
>>> was unsure whether the same flag can be used to indicate the iTXQ stop
>>> condition.
>>> I could not find any better name for this:-).
>> Hmm, yeah, not sure whether the two code paths can stomp on each other
>> if you reuse the flag. It would be neat to be able to reuse it, though...
>>
>> Otherwise, how about renaming the old one to _STOP_AGGR and calling the
>> new one _STOP_NETIF or something?
>
> These ones are much better, thanks toke!!
> I would probably like to extend the name to _STOP_NETIF_TX; how about=20
> keeping the old one as is=C2=A0 and renaming _TXQ_PAUSED to
> _TXQ_STOP_NETIF_TX ?
Sure, that works as well :)
-Toke
next prev parent reply other threads:[~2018-07-10 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 12:26 [PATCHv2] mac80211: add stop/start logic for software TXQs Manikanta Pubbisetty
2018-07-10 12:58 ` Toke Høiland-Jørgensen
2018-07-10 15:04 ` Manikanta Pubbisetty
2018-07-10 15:22 ` Toke Høiland-Jørgensen
2018-07-10 16:27 ` Manikanta Pubbisetty
2018-07-10 17:39 ` Toke Høiland-Jørgensen [this message]
2018-07-10 16:03 ` kbuild test robot
2018-07-10 16:12 ` Manikanta Pubbisetty
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=87fu0rc7mu.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 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).