linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Cc: Felix Fietkau <nbd@nbd.name>, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH] mac80211: don't put null-data frames on the normal TXQ
Date: Tue, 03 Jul 2018 16:31:09 +0200	[thread overview]
Message-ID: <87601wfl1u.fsf@toke.dk> (raw)
In-Reply-To: <20180703124725.30917-1-johannes@sipsolutions.net>

Johannes Berg <johannes@sipsolutions.net> writes:

> From: Johannes Berg <johannes.berg@intel.com>
>
> Since (QoS) NDP frames shouldn't be put into aggregation nor are
> assigned real sequence numbers, etc. it's better to treat them as
> non-data packets and not put them on the normal TXQs, for example
> when building A-MPDUs they need to be treated specially, and they
> are more used for management (e.g. to see if the station is alive)
> anyway.

No objections to this per se; but didn't we want to move towards
everything going through the TXQs? Any progress on that front? :)

-Toke

  reply	other threads:[~2018-07-03 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 12:47 [PATCH] mac80211: don't put null-data frames on the normal TXQ Johannes Berg
2018-07-03 14:31 ` Toke Høiland-Jørgensen [this message]
2018-07-03 14:32   ` Johannes Berg
2018-07-03 14:36     ` Toke Høiland-Jørgensen
2018-07-03 20:40 ` Peter Oh
2018-07-03 23:48   ` Johannes Berg
2018-07-04  4:24     ` Ben Greear
2018-07-04  7:12       ` Johannes Berg
2018-07-04  7:26     ` Toke Høiland-Jørgensen
2018-07-04  7:54       ` Johannes Berg
2018-07-04  8:25         ` Toke Høiland-Jørgensen

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=87601wfl1u.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    /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).