From: Ben Greear <greearb@candelatech.com>
To: Richard Farina <sidhayn@gmail.com>
Cc: Nick Kossifidis <mickflemm@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] This allows ath5k to support virtual STA and AP interfaces.
Date: Fri, 24 Sep 2010 12:40:17 -0700 [thread overview]
Message-ID: <4C9CFEA1.2080902@candelatech.com> (raw)
In-Reply-To: <4C9CFD4E.10401@gmail.com>
On 09/24/2010 12:34 PM, Richard Farina wrote:
> Nick Kossifidis wrote:
>> 2010/9/23 <greearb@candelatech.com>:
>>> From: Ben Greear <greearb@candelatech.com>
>>>
>>> +#define ATH5K_VIF_MAX 2048
>>
>> This is too much !!! 2048 interfaces with a total of 4 beacon buffers
>> 40 rx buffers and 200 tx buffers ? Has anyone tested this ?
>>
>> Also think about embedded devices, we don't want to waste memory like
>> this...
>>
> As a sanity check, I can say I've seen AP vendors that permit 32 SSIDs
> each with a unique BSSID/encryption, etc. I've never seen any device
> that does more than that so 32 is a pretty reasonable max vif (the user
> can always change it if desired, I'm looking at you openwrt team). Just
> my 0.02$
Many standard off-the-shelf APs seem to support more than that, and certainly
hostapd based APs can. Maybe it could be 512 and let users on very tight
systems carry a small patch to make it smaller for their particular needs?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-09-24 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 20:07 [PATCH v2] This allows ath5k to support virtual STA and AP interfaces greearb
2010-09-24 17:46 ` Nick Kossifidis
2010-09-24 18:17 ` Ben Greear
2010-09-24 21:49 ` Nick Kossifidis
2010-09-25 9:14 ` Felix Fietkau
2010-09-27 18:57 ` Ben Greear
2010-09-27 19:31 ` Felix Fietkau
2010-09-24 19:34 ` Richard Farina
2010-09-24 19:40 ` Ben Greear [this message]
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=4C9CFEA1.2080902@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.com \
--cc=sidhayn@gmail.com \
/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.