linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: jirislaby@gmail.com, mickflemm@gmail.com,
	mcgrof@do-not-panic.com, linux-wireless@vger.kernel.org,
	kvalo@codeaurora.org
Subject: Low latency communication over wifi
Date: Wed, 23 Sep 2015 13:03:43 +0200	[thread overview]
Message-ID: <20150923110343.GA19160@amd> (raw)

Hi!

I'm trying to transfer some audio data over wifi. Latency constrains
are such that if it would took more than 20msec to wait for
transmission, the packet should be dropped instead, and new one should
be transmitted.

My final hardware contains CSR6026 chip, but drivers are way too
ugly, I decided it would be easier to prototype on ath5k-based card.

I hacked qcu.c to limit latencies:

  	  qi->tqi_cw_min = ath5k_cw_validate(0);
          qi->tqi_cw_max = ath5k_cw_validate(20);

...but I don't think it did what I wanted. What am I missing?

(I could use Intel 3945ABG-based card instead, but I figured out ath5k
might be easier to hack?)

Is there way to manipulate type of service from userland to get
similar behaviour without patching kernel?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

             reply	other threads:[~2015-09-23 11:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 11:03 Pavel Machek [this message]
2015-09-23 11:21 ` Low latency communication over wifi Johannes Berg
2015-09-26 10:24   ` Pavel Machek
2015-09-28  7:41     ` Johannes Berg
2015-09-28 12:15       ` Bastian Bittorf
2015-09-28 12:37         ` Johannes Berg
2015-09-28 12:52           ` Bastian Bittorf
2015-09-30 17:24       ` Pavel Machek
2015-09-30 17:33         ` Bastian Bittorf
2015-09-30 18:28         ` Johannes Berg
2015-09-23 11:27 ` ath5k filling logs (was Re: Low latency communication over wifi) Pavel Machek
2015-09-23 11:42 ` Low latency communication over wifi Bastian Bittorf

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=20150923110343.GA19160@amd \
    --to=pavel@ucw.cz \
    --cc=jirislaby@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mickflemm@gmail.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).