linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonis Hadjiantonis <contact@antonis.mobi>
To: linux-wireless@vger.kernel.org
Subject: ath9k rate control statistics not updated for UDP
Date: Mon, 11 Jun 2012 13:37:08 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120611T152810-2@post.gmane.org> (raw)

I am using iperf to test rate control algorithms (use default:minstrel_ht) on an
ath9k device (WRT160NL OpenWRT Backfire 10.3.1 r29592). 
When I use UDP traffic over an 802.11g connection, the rcstat file is not
updated. Not sure if the rate control algoritmh works during the process.
If I use TCP traffic, rcstat is updated and statistics/rate change accordingly.

Is this the correct behaviour of minstrel RC? I went through documentation
regarding MRR and retransmission bounds but wasn't able to figure it out. Any
one noticed something similar?

Thanks in advance,
Antonis


             reply	other threads:[~2012-06-11 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 13:37 Antonis Hadjiantonis [this message]
2012-06-11 17:52 ` ath9k rate control statistics not updated for UDP Ben Greear
2012-06-12 10:17   ` Antonis Hadjiantonis

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=loom.20120611T152810-2@post.gmane.org \
    --to=contact@antonis.mobi \
    --cc=linux-wireless@vger.kernel.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).