From: "Michael Büsch" <mb@bu3sch.de>
To: b43-dev@lists.infradead.org
Subject: AW: 802.11 MAC state information
Date: Tue, 08 Feb 2011 16:28:53 +0100 [thread overview]
Message-ID: <1297178933.29400.16.camel@maggie> (raw)
In-Reply-To: <00dc01cbc7a3$dbcc0a10$93641e30$@gmx.net> (sfid-20110208_102132_361673_7C2434FF)
On Tue, 2011-02-08 at 16:21 +0100, h2o-post wrote:
> I would like to sample if the Broadcom wifi card (MAC) is transmitting, receiving or idle over time.
> Within the Atheros hardware there are register counters that count if one of the above - I call them - mac-state are present.
> Which those measurements I am looking into airtime consumption of different packets for sending and receiving.
> For example: 1500Byte udp packet causes the sender wifi card @54Mbit to be busy by this transmission for 240 micro sec (what I measure in the Atheros hardware is a txcounter increase by ~9600 ticks @40MHz)... also quite interesting are the distributions of receiving states over time and cca channel sensing busy over time.
> I have implemented I quite fast mechanism to read/dump the Atheros registers to a trace file in order to validate different upper layer traffic patterns/settings. I would like to extend this measurement to Broadcom hardware as well.
> For Atheros also the wprobe-utility from nbd, a nice tool that make use out of this "mac-state" over time measurements, maybe you have heard about it ?
>
> Does this make sense to you what I am interested in ?
The best and most accurate way to achieve this certainly is to
modify the firmware.
I don't know if the stock firmware provides enough information for
this without modification. You'll probably have to dig through the
specs wiki.
--
Greetings Michael.
prev parent reply other threads:[~2011-02-08 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 10:36 802.11 MAC state information h2o-post
2011-02-08 14:27 ` Michael Büsch
2011-02-08 15:21 ` AW: " h2o-post
2011-02-08 15:28 ` Michael Büsch [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=1297178933.29400.16.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.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).