From: Johannes Berg <johannes@sipsolutions.net>
To: Mathy Vanhoef <vanhoefm@gmail.com>, radiotap@netbsd.org
Subject: Re: Proposed Tx flag: don't reorder frames
Date: Fri, 24 Jul 2020 13:13:51 +0200 [thread overview]
Message-ID: <1f5e4f999c980e86ebec213b0b3bfcd9d22ede15.camel@sipsolutions.net> (raw)
In-Reply-To: <CAFXAJYyqgCqhMB0sEY4t5K-PcCe4G1O6Ef1NYCpK=eZcuntVvw@mail.gmail.com>
On Fri, 2020-07-24 at 09:58 +0400, Mathy Vanhoef wrote:
> I propose to add a DONT_REORDER bit to the existing TX flags field.
> When this flag is set, injected frames shouldn't be reordered relative
> to other frames that also have this flag set (even when these frames
> have different QoS TID values).
>
> This for example allows userspace to inject frames that have different
> QoS TID fields while assuring that they are transmitted in the order
> as they were injected. In practice this is useful to perform certain
> experiments where the order of transmitted frames is important.
Interesting.
> Note that on the radiotap website the TX flags field is still listed
> under the "suggested fields" page, but I'm assuming that by now this
> field is approved (since it's used in Linux)?
No, it never was. I made an attempt at some point, but abandoned it for
some reason.
I see no reason why it couldn't be done though, and I guess this new
flag could be included from the start.
johannes
next prev parent reply other threads:[~2020-07-24 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 5:58 Proposed Tx flag: don't reorder frames Mathy Vanhoef
2020-07-24 11:13 ` Johannes Berg [this message]
2020-08-30 0:05 ` Mathy Vanhoef
2020-09-17 9:57 ` Johannes Berg
2020-10-01 5:59 ` Mathy Vanhoef
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=1f5e4f999c980e86ebec213b0b3bfcd9d22ede15.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=radiotap@netbsd.org \
--cc=vanhoefm@gmail.com \
/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).