All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: add stop/start logic for software TXQs
Date: Tue, 03 Jul 2018 11:45:18 +0200	[thread overview]
Message-ID: <1530611118.4735.13.camel@sipsolutions.net> (raw)
In-Reply-To: <87345305-94d2-7c5e-379e-757670b7e59f@codeaurora.org>

On Mon, 2018-07-02 at 14:48 +0530, Manikanta Pubbisetty wrote:
> > 
> > > @@ -298,10 +354,15 @@ static void __ieee80211_wake_queue(struct ieee80211_hw *hw, int queue,
> > >   	if (local->q_stop_reasons[queue][reason] == 0)
> > >   		__clear_bit(reason, &local->queue_stop_reasons[queue]);
> > >   
> > > +	if (local->ops->wake_tx_queue)
> > > +		__clear_bit(reason, &local->txqs_stopped);
> > > +
> > >   	if (local->queue_stop_reasons[queue] != 0)
> > >   		/* someone still has this queue stopped */
> > >   		return;
> > >   
> > > +	ieee80211_wake_txqs(local);
> > 
> > I'm not sure this is the right place to hook in?
> > 
> > This might interact really strangely with drivers - which also get here.
> > Perhaps we should make this conditional on reason != DRIVER?
> 
> Good point!  IMO the condition (reason != DRIVER) does not fit well; if 
> the reason for stop queues is DRIVER then we don't get a chance to wake 
> them again. May be deferring the wake_txqs by scheduling a tasklet 
> should help?

Not sure what you mean? But I see what I said was also confusing.

What I meant is that we should just not allow the driver to stop the
TXQs this way - if it's a TXQ driver then it should just stop scheduling
if it needs to, it shouldn't continue scheduling and rely on us blocking
it.

We, for mac80211's purposes, need to stop, cannot influence scheduling
and want to unify it with the 'normal' queue stop - so my thought would
be that we should only set the TXQ to stopped if the reason isn't
DRIVER.

johannes

      reply	other threads:[~2018-07-03  9:45 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
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 [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=1530611118.4735.13.camel@sipsolutions.net \
    --to=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.