linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>, linux-wireless@vger.kernel.org
Cc: egrumbach@gmail.com
Subject: Re: [PATCH 1/2] mac80211: add A-MSDU tx support
Date: Tue, 23 Feb 2016 14:05:31 +0100	[thread overview]
Message-ID: <1456232731.9910.4.camel@sipsolutions.net> (raw)
In-Reply-To: <56CC4CAC.4080501@openwrt.org>

On Tue, 2016-02-23 at 13:12 +0100, Felix Fietkau wrote:
> 
> It's initialized to 0 by default, in which case it does not limit the
> A-MSDU size. The driver does not need to set it, but it really
> should.

Right, but this is problematic as Emmanuel had pointed out, when
scaling down you run into problems. Not sure we want that as the
default when the driver doesn't do anything?

Documenting it as we discussed should be good enough though I guess.

> > Apart from that, I'm not sure that having a field here that works
> > like
> > this is a good idea at all - all the other fields in the vicinity
> > kinda
> > go from mac80211 to the driver, where here you have something that
> > potentially goes from the driver to mac80211. Perhaps we can find a
> > better way of doing this?
> Didn't find a better place to put it. Got any ideas?

Not off the top of my head, sorry.

> > > + * @max_tx_fragments: maximum fragments per (A-)MSDU.
> > 
> > "fragments" is a bit unclear - I guess this should refer to
> > fraglist
> > length only? Or is it meant to apply as a limit to the sum of
> > pieces in
> > the fraglist? I think that should be clarified.
> Sum of 1 (head) + n_frags for each skb in the fraglist.

Clarify the comment? :)

> Yes. If A-MSDU in A-MPDU is not supported, dealing with starting and
> stopping of A-MPDU sessions leaves all kinds of nasty corner cases
> (since the txq is not flushed between sessions). In that case it's
> better to just leave it disabled from that point on.

Fair enough. You should be able to deal with it with the SSN, but that
might be difficult.

Actually, mac80211 on its own assigns the seqno so frames already on
the txq would not become part of the session, so we should be OK
without much effort?

> Yes. I'm relying on fast_tx fields to simplify dealing with headers
> and to avoid adding extra checks for all kinds of stuff like no
> software crypto, which ieee80211_check_fast_xmit already handles.
> 

Ok, makes sense.

johannes

  reply	other threads:[~2016-02-23 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 18:39 [PATCH 1/2] mac80211: add A-MSDU tx support Felix Fietkau
2016-02-18 18:39 ` [PATCH 2/2] mac80211: minstrel_ht: set A-MSDU tx limits based on selected max_prob_rate Felix Fietkau
2016-02-23 11:25 ` [PATCH 1/2] mac80211: add A-MSDU tx support Johannes Berg
2016-02-23 12:12   ` Felix Fietkau
2016-02-23 13:05     ` Johannes Berg [this message]
2016-02-23 19:03       ` Felix Fietkau
2016-02-23 12:16 ` 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=1456232731.9910.4.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=egrumbach@gmail.com \
    --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 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).