Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA
Date: Tue, 09 Jul 2013 11:34:25 +0200	[thread overview]
Message-ID: <51DBD921.3040704@rempel-privat.de> (raw)
In-Reply-To: <51DBD55B.2010204@openwrt.org>

Am 09.07.2013 11:18, schrieb Felix Fietkau:
> 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
>

Not with ath9k_htc. AdHock+BATMAN can be split in different groups on 
different channels. ath9k_htc can be used as STA to  primer AP and 
second interface on some laptops. But sure -- it is worst case scenario 
with no extra cost.

-- 
Regards,
Oleksij

  reply	other threads:[~2013-07-09  9:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  8:35 [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA David Jardin
2013-07-08 20:07 ` Adrian Chadd
2013-07-09  8:46   ` David Jardin
2013-07-09  8:50     ` Oleksij Rempel
2013-07-09  9:18       ` Felix Fietkau
2013-07-09  9:34         ` Oleksij Rempel [this message]
2013-07-09  9:52           ` Felix Fietkau
2013-07-09 11:23     ` Adrian Chadd
2013-11-20 18:44 ` Gustavo
2013-11-20 18:58   ` Ben Greear
2013-11-20 19:01     ` Gustavo Azambuja
2013-11-22 10:23       ` Oleksij Rempel
2013-11-22 14:40         ` Ben Greear
2013-11-22 14:47           ` Oleksij Rempel
2013-11-22 15:00             ` Ben Greear
2013-11-22 15:02               ` Oleksij Rempel
2013-11-22 15:10                 ` Ben Greear
2013-11-25 10:52               ` Alex Hacker
2013-11-25 11:45                 ` Sujith Manoharan
2013-11-25 12:02                   ` Alex Hacker
2013-11-25 19:19                     ` Adrian Chadd
2013-11-25 19:28                       ` Ben Greear
2013-11-25 20:19                         ` Adrian Chadd
2013-11-26  7:24                           ` Alex Hacker
2013-11-26  8:18                             ` Adrian Chadd
  -- strict thread matches above, loose matches on Subject: below --
2013-11-22 15:33 Trevor Cullen
2013-11-23  1:35 ` Sujith Manoharan
2013-11-25 11:27 Trevor Cullen
2013-11-25 11:57 ` Alex Hacker
2013-11-25 11:41 Trevor Cullen
2013-11-25 11:41 ` Sujith Manoharan

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=51DBD921.3040704@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=ath9k-devel@lists.ath9k.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