All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Taht <d@teklibre.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] oprofile the ath9k for low throughput rate and 3	questions
Date: Wed, 28 Apr 2010 08:17:47 -0600	[thread overview]
Message-ID: <4BD8438B.4070503@teklibre.org> (raw)
In-Reply-To: <8CCAE3CBA5A9F88-AB4-97F2@webmail-m009.sysops.aol.com>

On 04/19/2010 07:05 PM, oiioeu at aol.com wrote:
>
> I got avg. 60Mbps of the throughput rate by iperf testing and had the 
> testing environment like below:
>
>
> OpenWrt:                       r18529 (I tried the latest r20851  and 
> the throughput rate could be even worse )
> AP && STA h/w platform: IXP425
> wireless module:             AR9280( 11na, HT40 )
> wireless driver: ath9k version matched OpenWrt r18529
> topology is like:               PC1 - STA - AP - PC2 ( ethernet 
> connection between PC1 and STA, AP and PC2, and the wireless
>                                       connection between STA and the 
> AP. iperf client on PC1 and iperf server on PC2 )
>
> then I added oprofile support to this throughput rate testing and had 
> the throughput rate decrease to avg 8Mbps, here are my questions:
> 1. whether the avg. 8Mbps of the throughput after adding the oprofile 
> support seemed to be reasonable?
> 2. why there were the warning messeges at the beginning of the 
> opreport result and does it matter or not?
> 3. anyone could point me is there anything abnormal from the opreport 
> messeges that lead to the low throughput in my case?
> the oprofile log are attached

Interesting. I've been meaning to get around to oprofiling my hardware 
(nanostation M5) one of these days  as I'd noted that I was achieving 
~70Mbit via iperf and seeing (via top) that the hardware was spending 
70% of its time in the "sirq" state. (whether or not that was the 
wireless or wired drivers doing that, I don't know).

oprofile tends to be high overhead unless there is special on-chip 
counter support.

As for this particular oprofile, I don't know, but it looks like 
ath9k_ioread32 is a good candidate for optimization, even without the 
huge oprofile slowdown....


>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20100428/cd7523f8/attachment.htm 

  reply	other threads:[~2010-04-28 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20  1:05 [ath9k-devel] oprofile the ath9k for low throughput rate and 3 questions oiioeu at aol.com
2010-04-28 14:17 ` Dave Taht [this message]
2010-04-28 16:48   ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2010-05-25  8:24 oiioeu at aol.com
2010-05-25 13:07 ` Peter Stuge
2010-05-25 15:51 ` Luis R. Rodriguez
2010-05-26  1:46 oiioeu at aol.com

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=4BD8438B.4070503@teklibre.org \
    --to=d@teklibre.org \
    --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 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.