From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 2/3] mac80211: Make use of the new F_TX_NOACK and F_TX_NOSEQ Radiotap TX flags
Date: Fri, 12 Dec 2008 23:56:38 +0100 [thread overview]
Message-ID: <1229122598.3565.22.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910812121451u25713c82o229a56006089edd6@mail.gmail.com> (sfid-20081212_235104_744345_FF8EB7B3)
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Fri, 2008-12-12 at 23:51 +0100, Stefanik Gábor wrote:
> But if we redefine !ASSIGN_SEQ to mean "use the sequence number
> supplied by userspace", we will need a new flag to distinguish between
> driver-level vs. stack-level sequence number assignments, which is
> essentially the same as this patch. There is no way to switch between
> 3 states (control in driver, stack or userspace) using only one bit.
No, wait, that's not true. We just have to make the bit be set to 1 by
default, and let radiotap or the stack clear it. Then if it's clear
after radiotap, the stack won't assign a seqno, and if it's still set
then the stack checks and assigns seq and/or clears it.
Might be easier to use the other bit though instead.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-12-12 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 22:32 [RFC 2/3] mac80211: Make use of the new F_TX_NOACK and F_TX_NOSEQ Radiotap TX flags Stefanik Gábor
2008-12-12 22:39 ` Johannes Berg
2008-12-12 22:43 ` Stefanik Gábor
2008-12-12 22:45 ` Johannes Berg
2008-12-12 22:51 ` Stefanik Gábor
2008-12-12 22:52 ` Johannes Berg
2008-12-12 23:00 ` Stefanik Gábor
2008-12-12 23:01 ` Johannes Berg
2008-12-12 22:56 ` 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=1229122598.3565.22.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@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