From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH RFC] ath9k: collect statistics about Rx-Dup and Rx-STBC packets
Date: Sun, 28 Apr 2013 16:13:11 +0200 [thread overview]
Message-ID: <517D2E77.8000104@rempel-privat.de> (raw)
In-Reply-To: <517D1B45.9020302@openwrt.org>
Am 28.04.2013 14:51, schrieb Felix Fietkau:
> On 2013-04-27 5:25 PM, Oleksij Rempel wrote:
>> Collect statistics about recived duplicate and STBC packets.
>> This information should help see if STBC is actually working.
>>
>> Tested on ar9285;
>>
>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
> I thought about this patch some more, and I'm wondering what's the point
> in doing this? These statistics are going to be completely useless for
> most people and they'll waste some memory/cpu cycles, especially on
> small-cache devices. I think it's much more useful to simply pass the
> information to mac80211 via rx flags and get them added to the radiotap
> header.
Sure.
> I'd like to keep the number of 'poor man's debug hacks' in the driver to
> a minimum,
well, i'll prefer it to call with my name: lazy man's hack ;)
> and there are some other things that I think should be
> removed: rx_frags and rx_beacons in struct ath_rx_stats, the tx/rx MAC
> sampling hack, and pretty much anything else that can be just as easily
> accessed from mac80211 through regular interfaces.
I think there is more things to do in ath9k. Create the list and we can
talk about it. For example one of it: I needed some time to understand
how some parts of code relate to the hardware. Especially Rx and Tx
descriptors. Some comments in header will help... I can add some of them
(may be it will help other beginners), but i afraid that i spend time
but my patches wont be included.
--
Regards,
Oleksij
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <linux@rempel-privat.de>
To: Felix Fietkau <nbd@openwrt.org>
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC] ath9k: collect statistics about Rx-Dup and Rx-STBC packets
Date: Sun, 28 Apr 2013 16:13:11 +0200 [thread overview]
Message-ID: <517D2E77.8000104@rempel-privat.de> (raw)
In-Reply-To: <517D1B45.9020302@openwrt.org>
Am 28.04.2013 14:51, schrieb Felix Fietkau:
> On 2013-04-27 5:25 PM, Oleksij Rempel wrote:
>> Collect statistics about recived duplicate and STBC packets.
>> This information should help see if STBC is actually working.
>>
>> Tested on ar9285;
>>
>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
> I thought about this patch some more, and I'm wondering what's the point
> in doing this? These statistics are going to be completely useless for
> most people and they'll waste some memory/cpu cycles, especially on
> small-cache devices. I think it's much more useful to simply pass the
> information to mac80211 via rx flags and get them added to the radiotap
> header.
Sure.
> I'd like to keep the number of 'poor man's debug hacks' in the driver to
> a minimum,
well, i'll prefer it to call with my name: lazy man's hack ;)
> and there are some other things that I think should be
> removed: rx_frags and rx_beacons in struct ath_rx_stats, the tx/rx MAC
> sampling hack, and pretty much anything else that can be just as easily
> accessed from mac80211 through regular interfaces.
I think there is more things to do in ath9k. Create the list and we can
talk about it. For example one of it: I needed some time to understand
how some parts of code relate to the hardware. Especially Rx and Tx
descriptors. Some comments in header will help... I can add some of them
(may be it will help other beginners), but i afraid that i spend time
but my patches wont be included.
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-04-28 14:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 15:25 [ath9k-devel] [PATCH RFC] ath9k: collect statistics about Rx-Dup and Rx-STBC packets Oleksij Rempel
2013-04-27 15:25 ` Oleksij Rempel
2013-04-27 18:39 ` [ath9k-devel] [PATCH v2] " Oleksij Rempel
2013-04-27 18:39 ` Oleksij Rempel
2013-04-27 18:51 ` [ath9k-devel] " Adrian Chadd
2013-04-27 18:51 ` Adrian Chadd
2013-04-27 18:53 ` [ath9k-devel] " Oleksij Rempel
2013-04-27 18:53 ` Oleksij Rempel
2013-04-27 19:06 ` [ath9k-devel] " Adrian Chadd
2013-04-27 19:06 ` Adrian Chadd
2013-04-27 19:13 ` [ath9k-devel] " Oleksij Rempel
2013-04-27 19:13 ` Oleksij Rempel
2013-04-28 1:21 ` [ath9k-devel] " Felix Fietkau
2013-04-28 1:21 ` Felix Fietkau
2013-04-28 6:41 ` [ath9k-devel] [PATCH v3] " Oleksij Rempel
2013-04-28 6:41 ` Oleksij Rempel
2013-04-28 12:51 ` [ath9k-devel] [PATCH RFC] " Felix Fietkau
2013-04-28 12:51 ` Felix Fietkau
2013-04-28 14:13 ` Oleksij Rempel [this message]
2013-04-28 14:13 ` Oleksij Rempel
2013-04-28 15:03 ` [ath9k-devel] " Oleksij Rempel
2013-04-28 15:03 ` Oleksij Rempel
2013-04-28 19:19 ` Oleksij Rempel
2013-04-28 19:19 ` Oleksij Rempel
2013-04-28 19:20 ` Felix Fietkau
2013-04-28 19:20 ` Felix Fietkau
2013-04-29 6:45 ` Wojciech Dubowik
2013-04-29 6:45 ` Wojciech Dubowik
2013-04-29 7:20 ` Oleksij Rempel
2013-04-29 7:20 ` Oleksij Rempel
2013-04-28 14:54 ` Ben Greear
2013-04-28 14:54 ` Ben Greear
2013-04-28 15:08 ` Felix Fietkau
2013-04-28 15:08 ` Felix Fietkau
2013-04-28 15:15 ` Ben Greear
2013-04-28 15:15 ` Ben Greear
2013-04-28 15:32 ` Felix Fietkau
2013-04-28 15:32 ` Felix Fietkau
2013-05-08 5:32 ` Sujith Manoharan
2013-05-08 5:32 ` Sujith Manoharan
2013-05-08 16:07 ` Ben Greear
2013-05-08 16:07 ` Ben Greear
2013-05-08 22:45 ` Adrian Chadd
2013-05-08 22:45 ` Adrian Chadd
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=517D2E77.8000104@rempel-privat.de \
--to=linux@rempel-privat.de \
--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.