From: Karl Beldan <karl.beldan@gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Felix Fietkau <nbd@openwrt.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4] mac80211/minstrel_ht: add support for using CCK rates
Date: Sun, 17 Mar 2013 23:40:19 +0100 [thread overview]
Message-ID: <20130317224019.GA7563@gobelin> (raw)
In-Reply-To: <CAJ-VmonRkrd5cw_k6uwMFBrvjz95fcDO7rJi5HY8grKeY6Jp5g@mail.gmail.com>
On Sun, Mar 17, 2013 at 03:30:17PM -0700, Adrian Chadd wrote:
> On 17 March 2013 15:07, Karl Beldan <karl.beldan@gmail.com> wrote:
>
> > The best way I could look at it was that it would let drivers know the frame is
> > being transmitted under BA, but it still changes the meaning and thus
> > the handling of the flag.
> > Frankly, if the meaning "officially" becomes "this frames is being
> > transmitted under BA", as the code behaves, and you seem to say, I am all
> > for it ;)
>
> Well, having it be "This frame is being transmitted under aggregation"
> can't be guaranteed anyway.
>
> Eg, imagine the case where your BA window is such that you've sent 0
> .. 63 and only received a BA for 1..63.
> So you have to send one single frame - why would you request a
> blockack and why would you transmit it as an aggregate? :)
>
When I wrote "under BA", I meant "under BlockAck Aggreement" not "will
be aggregated" ;)
Karl
prev parent reply other threads:[~2013-03-17 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 9:51 [PATCH v4] mac80211/minstrel_ht: add support for using CCK rates Felix Fietkau
2013-02-13 9:57 ` Johannes Berg
2013-03-12 9:41 ` Karl Beldan
2013-03-15 15:36 ` Johannes Berg
2013-03-17 21:23 ` Karl Beldan
2013-03-17 21:46 ` Felix Fietkau
2013-03-17 22:07 ` Karl Beldan
2013-03-17 22:30 ` Adrian Chadd
2013-03-17 22:40 ` Karl Beldan [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=20130317224019.GA7563@gobelin \
--to=karl.beldan@gmail.com \
--cc=adrian@freebsd.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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.