All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 3/3] mac80211: Allow overriding some HT information.
Date: Fri, 04 Nov 2011 09:27:26 -0700	[thread overview]
Message-ID: <4EB4126E.1020802@candelatech.com> (raw)
In-Reply-To: <1320423893.3969.104.camel@jlt3.sipsolutions.net>

On 11/04/2011 09:24 AM, Johannes Berg wrote:
> On Fri, 2011-11-04 at 09:17 -0700, Ben Greear wrote:
>
>>>>> The AMPDU density should only allow increasing.
>>>>>
>>>>> I think a lot of this validation should live in cfg80211 so if another
>>>>> driver wants to implement it, this kind of thing is already covered.
>>>>
>>>> The ath9k driver supports 0, and then every value that corresponds to 1us or higher.
>>>> If you set it to 1/2us, for instance, it just quietly rounds up to 1us.  It defaults
>>>> to 8, so it appears valid to decrease or increase this value.
>>>
>>> What quietly rounds up?
>>>
>>> If it defaults to 8 then I'm sure there's a reason for it, such as the
>>> crypto engine not being fast enough and needing 8us buffer between
>>> frames. As such, I really don't think decreasing it is valid.
>>
>> See this code in ath9k, top of main.c.  It appears to support more
>> than the default of 8.  I tested it out, and it appears to work
>> when set to lower values.  I am disabling hw-crypt since I need
>> multiple VIFS, but not sure that matters or not.
>>
>> static u8 parse_mpdudensity(u8 mpdudensity)
>
> Well, this is used for TX. You're advertising the value for RX.
> Advertising a smaller value may work for you -- but only if the AP uses
> something larger anyway. It's free to do this. The code you quoted
> implements this -- it looks at what the min spacing is the peer wants,
> and then uses something bigger.
>
> So I still stand by what I said earlier -- you should not allow
> advertising a smaller value than the hardware wanted to use initially.
> If the AP doesn't use that smaller value, all is well, but if it
> actually uses a smaller value then the hardware might fall over.

Ok, I'll add that restriction.  When this all settles, maybe I
can get some info from the ath9k folks about what their hardware
can actually support.

Thanks,
Ben

>
> johannes


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


  reply	other threads:[~2011-11-04 16:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  5:55 [PATCH v3 1/3] mac80211: Support forcing station to disable HT (802.11n) greearb
2011-11-03  5:55 ` [PATCH v3 2/3] mac80211: Support disabling ht40 greearb
2011-11-03  5:55 ` [PATCH v3 3/3] mac80211: Allow overriding some HT information greearb
2011-11-03  8:47   ` Johannes Berg
2011-11-03 17:13     ` Ben Greear
2011-11-04 14:41       ` Johannes Berg
2011-11-04 16:17         ` Ben Greear
2011-11-04 16:24           ` Johannes Berg
2011-11-04 16:27             ` Ben Greear [this message]
2011-11-04 16:30               ` Johannes Berg
2011-11-03  8:37 ` [PATCH v3 1/3] mac80211: Support forcing station to disable HT (802.11n) Johannes Berg
2011-11-03 17:18   ` Ben Greear
2011-11-04 14:38     ` Johannes Berg

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=4EB4126E.1020802@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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.