From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Cc: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
G?bor Stefanik
<netrolller.3d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Proposal]TX flags
Date: Thu, 16 Apr 2009 15:48:06 -0500 [thread overview]
Message-ID: <20090416204806.GD25412@ojctech.com> (raw)
In-Reply-To: <200904162110.05150.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
On Thu, Apr 16, 2009 at 09:10:04PM +0200, Michael Buesch wrote:
> On Thursday 16 April 2009 20:59:34 Johannes Berg wrote:
> > On Thu, 2009-04-16 at 20:47 +0200, G?bor Stefanik wrote:
> >
> > > Alternatively, the meanings of the {0,0} and {1,1} cases could be
> > > switched around (making the {0,0} case more logical, at the expense of
> > > the {1,1} one):
> > >
> > > TX Flags absent: Use RTS & CTS as needed.
> > > TX Flags present: {
> > > RTS=0, CTS=0: Use RTS & CTS as needed.
> > > RTS=0, CTS=1: Use CTS-to-self.
> > > RTS=1, CTS=0: Use RTS/CTS-handshake.
> > > RTS=1, CTS=1: Use neither RTS nor CTS.
>
> The first and the last thing let my head explode, because it's not
> what somebody would expect from such bits. This kind of logic is also
> used in wext. And it's why I hate wext. "bit0 means x, bit1 means y,
> buuuuuuuuuuuuuuuut iff both bits are set the whole logic is inverted
> and whatever..." That complicates _every_ single test of the bit
> (always need if (bit0 is set but not bit1)) It produces spaghetti code
> interpreting these bits with lots of branches and special conditions
> that nobody does understand by reading the code alone. If you can't
> encode your functionality into a boolean, do _NOT_ use bits to encode
> it. Use integers to encode tristate or quadstate or whatever. You
> essentially _did_ that already, if you look at your bits. You use the
> two individual bits as 2bit integer value. So why not spell it out and
> use an integer field for that information?
G?bor,
I see the point that Michael is making. What do you think? Shall
we treat it as a 2-bit wide unsigned integer field in the Tx flags,
instead?
Dave
--
David Young OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org Urbana, IL * (217) 278-3933
next prev parent reply other threads:[~2009-04-16 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:33 [Proposal]TX flags Gábor Stefanik
[not found] ` <69e28c910904141733m72ce521ap8f1865bec991fff7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 15:37 ` David Young
2009-04-16 17:28 ` Johannes Berg
[not found] ` <1239902910.26575.14.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-04-16 18:47 ` Gábor Stefanik
[not found] ` <69e28c910904161147h5a68d3b5nd054b043d6ad2719-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 18:59 ` Johannes Berg
[not found] ` <1239908374.26575.20.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-04-16 19:10 ` Michael Buesch
[not found] ` <200904162110.05150.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2009-04-16 20:48 ` David Young [this message]
[not found] ` <20090416204806.GD25412-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-04-17 1:24 ` Gábor Stefanik
[not found] ` <69e28c910904161824t7af6860dxebf3a13069b924d5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-17 9:50 ` Johannes Berg
2009-04-16 20:33 ` David Young
[not found] ` <20090416203353.GC25412-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-04-16 20:48 ` Johannes Berg
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=20090416204806.GD25412@ojctech.com \
--to=dyoung-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netrolller.3d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.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).