From: Bob Copeland <me@bobcopeland.com>
To: Sam Leffler <sleffler@google.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
Thomas Pedersen <thomas@cozybit.com>,
ath5k-devel@lists.ath5k.org, jirislaby@gmail.com,
mickflemm@gmail.com, mcgrof@qca.qualcomm.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: RX timestamp is reported at end of frame
Date: Mon, 12 Nov 2012 23:32:26 -0500 [thread overview]
Message-ID: <20121113043226.GA4064@localhost> (raw)
In-Reply-To: <CA+yqC4ZkeKgLKoPh18f1qDyLuOGf22GyL92+suca+gveoq7ZVw@mail.gmail.com>
On Mon, Nov 12, 2012 at 11:40:15AM -0800, Sam Leffler wrote:
> > I'll do some testing tonight with whatever cards I have around here to
> > see if we can at least get a better idea of which chipsets do what.
>
> >From my experience doing tdma on ath chipsets I know the timestamp is
> a snapshot of the tsf recorded by the dma engine when it writes the
> descriptor on dma completion. This was only legacy frames; don't know
> how things work for aggregate frames.
On dma completion, so that might be even a bit further beyond
end-of-frame?
For the record, I just tested this as follows: I set up a mesh
network between an ath5k and an ath9k card (the ath9k driver being
already patched similarly), with the mesh beacon having a few
information elements, and operating in 2.4 GHz band.
Then I watched toffset adjustments. A more accurate timestamp
means the toffsets between the stations should be closer to each
other.
Here are some representative numbers:
ath5k: phy2: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
-------------------------------------------------------------
Without patch:
updated toffset for 00:80:48:63:a2:f8: 52987952
updated toffset for 00:03:7f:10:4d:d6: -52989071
(diff 1119 us)
With patch:
updated toffset for 00:80:48:63:a2:f8: -92733857
updated toffset for 00:03:7f:10:4d:d6: 92733496
(diff 361 us)
ath5k: phy0: Atheros 5414 chip found (MAC: 0xa3, PHY: 0x61)
-------------------------------------------------------------
Without patch:
updated toffset for 00:17:f2:43:be:3a: -2557256031
updated toffset for 00:03:7f:10:4d:d6: 2557254935
(diff 1096 us)
With patch:
updated toffset for 00:17:f2:43:be:3a: -2054754842
updated toffset for 00:03:7f:10:4d:d6: 2054755003
(diff 161 us)
Sorry, those are all the ath5k devices I have access to without
digging through some boxes, but in the absence of someone with
old old hardware showing up and saying this is worse for them,
I'd say ship it...
Thomas, feel free to add my:
Tested-by: Bob Copeland <me@bobcopeland.com>
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2012-11-13 4:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:53 [PATCH] ath5k: RX timestamp is reported at end of frame Thomas Pedersen
2012-11-12 19:17 ` Adrian Chadd
2012-11-12 19:28 ` Bob Copeland
2012-11-12 19:40 ` Sam Leffler
2012-11-12 19:47 ` Adrian Chadd
2012-11-13 4:32 ` Bob Copeland [this message]
2012-11-13 11:33 ` Nick Kossifidis
2012-11-13 16:27 ` Sam Leffler
2012-11-14 17:49 ` Bob Copeland
-- strict thread matches above, loose matches on Subject: below --
2012-11-13 18:48 Thomas Pedersen
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=20121113043226.GA4064@localhost \
--to=me@bobcopeland.com \
--cc=adrian@freebsd.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=mickflemm@gmail.com \
--cc=sleffler@google.com \
--cc=thomas@cozybit.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).