From mboxrd@z Thu Jan  1 00:00:00 1970
From: Felix Fietkau <nbd@openwrt.org>
Date: Tue, 09 Jul 2013 11:18:19 +0200
Subject: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA
In-Reply-To: <51DBCEBE.7010405@rempel-privat.de>
References: <51DA79B6.8030702@djardin.de>
	<CAJ-VmonQcx=G+dM40c1GY6z2UmnUrC+QORwhSxh1Pu1rOynEGg@mail.gmail.com>
	<51DBCE01.5030406@djardin.de> <51DBCEBE.7010405@rempel-privat.de>
Message-ID: <51DBD55B.2010204@openwrt.org>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On 2013-07-09 10:50 AM, Oleksij Rempel wrote:
> How replacing AP with about MESH or AdHock+BATMAN?
Why? That sounds like a recipe for disaster to me (at least for
conference networks). The ath9k_htc stuff can't handle more peers in
mesh/ad-hoc than clients in AP mode.
In setting up a conference network, you have to think about what the
primary bottleneck is. When using consumer APs, the bottleneck isn't
CPU/RAM, it's usually limited channel airtime!

- Felix