Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: David Jardin <ich@djardin.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA
Date: Tue, 09 Jul 2013 10:46:57 +0200	[thread overview]
Message-ID: <51DBCE01.5030406@djardin.de> (raw)
In-Reply-To: <CAJ-VmonQcx=G+dM40c1GY6z2UmnUrC+QORwhSxh1Pu1rOynEGg@mail.gmail.com>

Hi Adrian,

thanks for the response. That's bad news.

I thought about using the Pi's as they have much more RAM and CPU power
than normal consumer access points have - which seems to be the limiting
factor of clients on those devices. And as we are a non profit
organization we simply can't afford business class access points (Cisco
etc.) as they are way to expensive.

David

Am 08.07.13 22:07, schrieb Adrian Chadd:
> The ath9k_htc stuff isn't ready to do what you want. And even if it
> was, the performance would be sub-par compared to the SoC designs.
> There's just not a lot of RAM on these things; even if we do
> eventually push almost everything into the driver instead of firmware,
> there's still only a limited amount of RAM for packet buffers. So
> you're never going to reach the same level of performance as
> direct-attach.
>
> I suggest you spend the money on some slightly more useful access
> points. You'll likely be able to serve at least 2x the clients on a
> single 2x2 tplink or dlink access point for about $50-$70 each.
>
> Good luck,
>
>
> -adrian
> (Why does everyone see "Raspberry pi" as the solution to everything
> these days? Sheesh..)
>
>
> On 8 July 2013 01:35, David Jardin <ich@djardin.de> wrote:
>> Hi,
>>
>> I'm organizing all the technical stuff for several conferences about
>> Joomla (opensource content managment system) with 200-300 participants
>> and therefore I was looking for a low-budget wifi-solution that is able
>> to handle this number of clients. I decided to use a few raspberry pi's
>> with atheros-based usb wifi dongles which worked great in my little test
>> environment but crashed in the real conference setup.
>>
>> I took a look at the logfiles and it seems that the issue is related to
>> the number of clients that can be handled by the driver/firmware, which
>> is 8 (ATH9K_HTC_MAX_STA). Is there any chance to increase this limit to
>> make the dongles usable in large-scale applications?
>>
>> David
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

  reply	other threads:[~2013-07-09  8:46 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 [this message]
2013-07-09  8:50     ` Oleksij Rempel
2013-07-09  9:18       ` Felix Fietkau
2013-07-09  9:34         ` Oleksij Rempel
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=51DBCE01.5030406@djardin.de \
    --to=ich@djardin.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