linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k: Still seeing DMA issues in latest wireless-testing.
Date: Sun, 30 Jan 2011 08:39:26 -0800	[thread overview]
Message-ID: <4D45943E.2050409@candelatech.com> (raw)
In-Reply-To: <AANLkTinSxnxYdUuQGWRr-fA8HF_JotQfG3S1QWEwS3K=@mail.gmail.com>

On 01/30/2011 07:54 AM, Björn Smedman wrote:
> On Sat, Jan 29, 2011 at 5:43 AM, Ben Greear<greearb@candelatech.com>  wrote:
>> Looks like some potentially nice ath9k patches just got merged into
>> wireless-testing.  It has been stable and fast so far, but I
>> do still see DMA issues in the logs.
>>
>> This is on a system with 30 STAs associated with a flakey netgear running
>> HT40-, and 30 associated with a cisco running HT20.  (Through some luck,
>> the netgear managed to send proper ht-info channel this time,
>> so the NIC went HT40-).
>
> Ben, the fact that you see much more of these DMA issues when you're
> running your virtual STAs suggests to me that root cause is some race
> condition between dma and cpu. The main difference between the 60 STA
> use-case and the one STA use case is that rx irq processing will take
> longer with multiple STAs, right? Is there some other difference?

I don't know.  I see it even when not running much traffic.

I also see DMA on my AP system, which has a single AP and one idle
station.  Granted, I have 128 or so stations connected to the AP,
but again, the stations are mostly idle.

Other folks see the DMA issues too...and most probably just don't report
them anymore...

Thanks,
Ben

>
> /Björn


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

      reply	other threads:[~2011-01-30 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29  4:43 ath9k: Still seeing DMA issues in latest wireless-testing Ben Greear
2011-01-30 15:54 ` Björn Smedman
2011-01-30 16:39   ` 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=4D45943E.2050409@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bjorn.smedman@venatech.se \
    --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 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).