linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] ath9k_hw: Fix slottime with coverage class
Date: Fri, 26 Aug 2011 17:00:04 +0200	[thread overview]
Message-ID: <4E57B4F4.9080007@openwrt.org> (raw)
In-Reply-To: <20110826133200.GA17491@vmraj-lnx.users.atheros.com>

On 2011-08-26 3:32 PM, Rajkumar Manoharan wrote:
> On Thu, Aug 25, 2011 at 05:36:03PM +0200, Felix Fietkau wrote:
>>  On 2011-08-25 4:45 PM, Rajkumar Manoharan wrote:
>>  >The commit b6ba41bb27eb9810d54e2301355ce56fd0e94a1a updates
>>  >acktimeout wihout updating slottime when coverage class is defined
>>  >as per IEEE 802.11-2007 17.3.8.6.
>>  >
>>  >Signed-off-by: Rajkumar Manoharan<rmanohar@qca.qualcomm.com>
>>  I intentionally left the coverage class out of the hw slot time
>>  setting, because increasing slot time too much causes severe
>>  throughput issues. I've observed this even with relatively minor
>>  coverage class settings (e.g. for 2 km) on AR9160 and AR9280. I
>>  haven't tested AR9380 though.
>>
> Which band have you tested on AR9280?
Both.

  reply	other threads:[~2011-08-26 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 14:45 [PATCH 1/2] ath9k_hw: Fix rx latency of 11a mode Rajkumar Manoharan
2011-08-25 14:45 ` [PATCH 2/2] ath9k_hw: Fix slottime with coverage class Rajkumar Manoharan
2011-08-25 15:36   ` Felix Fietkau
2011-08-26 13:32     ` Rajkumar Manoharan
2011-08-26 15:00       ` Felix Fietkau [this message]
2011-08-26 15:20         ` Rajkumar Manoharan
2011-08-26 15:26           ` Felix Fietkau
2011-08-25 15:32 ` [PATCH 1/2] ath9k_hw: Fix rx latency of 11a mode Felix Fietkau
2011-08-26  5:04   ` Rajkumar 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=4E57B4F4.9080007@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rmanohar@qca.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).