All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Default rates for broadcast, multicast, and management frames?
Date: Tue, 15 Sep 2015 11:20:08 -0700	[thread overview]
Message-ID: <55F86158.2090907@candelatech.com> (raw)

ath10k firmware allows one to set fixed rates for broadcast, multicast, and management/beacon
frames.  I think upstream firmware may not have full support, but the API is there in 10.1,
at least, and CT firmware has full support.

I think the defaults are 6Mbps, but not certain of that.

CT kernels have a patch that gives debugfs access to set this, and I am also
working on automatically decreasing the rate down to 1Mbps if user has specified
only /b legacy rates, etc.

Instead of using whatever the firmware chooses for defaults, I think it is
better if the driver explicitly set the rates as desired.

So, what are the suggested defaults for these rate types?  Stick with 6Mbps for
/b/g and /a modes?  Set to 1Mbps of /b mode?  Different defaults for different
types?

Also, at least some ucast/bcast frames may be turned into directed frames and
then it may use normal peer rate-ctrl logic, as far as I remember.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Default rates for broadcast, multicast, and management frames?
Date: Tue, 15 Sep 2015 11:20:08 -0700	[thread overview]
Message-ID: <55F86158.2090907@candelatech.com> (raw)

ath10k firmware allows one to set fixed rates for broadcast, multicast, and management/beacon
frames.  I think upstream firmware may not have full support, but the API is there in 10.1,
at least, and CT firmware has full support.

I think the defaults are 6Mbps, but not certain of that.

CT kernels have a patch that gives debugfs access to set this, and I am also
working on automatically decreasing the rate down to 1Mbps if user has specified
only /b legacy rates, etc.

Instead of using whatever the firmware chooses for defaults, I think it is
better if the driver explicitly set the rates as desired.

So, what are the suggested defaults for these rate types?  Stick with 6Mbps for
/b/g and /a modes?  Set to 1Mbps of /b mode?  Different defaults for different
types?

Also, at least some ucast/bcast frames may be turned into directed frames and
then it may use normal peer rate-ctrl logic, as far as I remember.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2015-09-15 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 18:20 Ben Greear [this message]
2015-09-15 18:20 ` Default rates for broadcast, multicast, and management frames? Ben Greear

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=55F86158.2090907@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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.