Skip to content

RFC SMP fixes: serialization and Disablig D1 and D2

W. van den Akker ath9k-devel 4 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 RFC Latest posting 4/40 of 4 patches 0 repliesNew
  2. v3 RFC posting 3/40 of 4 patches 0 repliesSuperseded
  3. v3 RFC posting 2/40 of 4 patches 0 repliesSuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v3 RFC posting 1/40 of 4 patches0 repliesSuperseded

Patches in v3 posting 4/4 No applies recorded yet

None of the 4 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [ath9k-devel] [RFC v3 0/4] SMP fixes: serialization and Disablig D1 and D2
Quoted 67 lines · W. van den Akker
Quoted 49 lines · On Friday 27 February 2009 20:18:31 W. van den Akker wrote:
Quoted 48 lines · On Friday 27 February 2009 20:00:40 Luis R. Rodriguez wrote:
Quoted 47 lines · W. van den Akker
Quoted 34 lines · On Tuesday 24 February 2009 07:33:57 Luis R. Rodriguez wrote:

From: Luis R. Rodriguez <[email protected]>

Ok, here's a respin of my SMP fixes series (previously just serialization). I got an SMP box at work now and did manage to get a PCI AR5416 card and did reproduce a hang.

The good news is the hang is gone but I'm not sure if this will fix the hangs reported here with AR5416 and SMP boxen so please give it a spin and let me know.

This also now deregisters the CPU notifier which we were not doing before.

This applies on top of today's wireless-testing. You can get the full set of 4 patches in one file here:

http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/ath9k/
20 09 -02- 24/serialization-v3.patch

I'd like a few reports on this, please let me know.

Luis R. Rodriguez (4):
ath9k: implement IO serialization
ath9k: AR9280 PCI devices must serialize IO as well
ath9k: add cpu notifier to enhance device configuration
ath9k: disable D1 and D2 on PCI multicore systems

 drivers/net/wireless/ath9k/ath9k.h |    7 ++++
 drivers/net/wireless/ath9k/hw.c    |   71

+++++++++++++++++++++++++++++++++++-
drivers/net/wireless/ath9k/hw.h

| 11 +++++-

Quoted 8 lines
 drivers/net/wireless/ath9k/main.c  |   30 +++++++++++++++
 drivers/net/wireless/ath9k/pci.c   |   46 +++++++++++++++++++++++
 5 files changed, 162 insertions(+), 3 deletions(-)

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

I have applied them on the wireless-testing tree from 25-2. Its running now....

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

To be continued....

How's it coming along with the patches.

Running since 26-2 17:00 (now 27 hours) without any problems. Looking good :)

Hmmm, Houston we have a problem.

When I updated my notebook (which is connected through a wifi connection) I got again a hang.
I updated it with 'aptitude update' to get a updated list with packages. There I got the first hang. After a restart of the server an 'aptitude full-update' caused a second hang.
So it looks like if there is a high load on the wifi-connection it causes a hang.

Quoted 2 lines

I will test it with 'iperf' to see if I can also reproduce it.

Did some testing with 'iperf'

Did about 20 tests whith 'iperf -c xxx'. Got 1 hang. Throughput about 12,8 Mbps
Did about 10 tests whith 'iperf -c xx -P 2' Got 8 hangs. Thoughpunt about 6 Mbps per session.

However not conclusive, but it looks like if there are more then 1 parallel sessions the server got a hangup.

Any thoughts about this...?

gr,
Willem

Signature · 3 lines
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.