From: Pavel Machek <pavel@ucw.cz>
To: Johannes Berg <johannes@sipsolutions.net>,
Bastian Bittorf <bittorf@bluebottle.com>
Cc: jirislaby@gmail.com, mickflemm@gmail.com,
mcgrof@do-not-panic.com, linux-wireless@vger.kernel.org,
kvalo@codeaurora.org
Subject: Re: Low latency communication over wifi
Date: Sat, 26 Sep 2015 12:24:03 +0200 [thread overview]
Message-ID: <20150926102403.GA21555@amd> (raw)
In-Reply-To: <20150923114236.GJ6319@medion.lan> <1443007312.1889.8.camel@sipsolutions.net>
Hi!
> > (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?
>
> If your AP has WMM/QoS then you can use setsockopt(SO_PRIORITY) to
> change the TID and thus the AC and get your packets classified as voice
> (VO) on wifi, which makes them much more likely to get access to the
> medium.
That would be equivalent to ping -Q, right? It does not seem to have
any effect :-(. I'd expect at least local machine to use shorter waits
for medium, and thus drop packets instead of waiting.
On Wed 2015-09-23 13:42:36, Bastian Bittorf wrote:
> * Pavel Machek <pavel@ucw.cz> [23.09.2015 13:38]:
> > Is there way to manipulate type of service from userland to get
> > similar behaviour without patching kernel?
>
> yes, iptables DSCP / DiffServ / Differentiated Services Field
>
> # you have to add some magic for matching your data
> e.g. $IPT -t mangle -I OUTPUT -j DSCP --set-dscp-class CS7
Again, this is ping -Q equivalent, right? I was doing
ping -c 300 -i .2 -Q $[56*4] -s 500 amd
300 packets transmitted, 300 received, 0% packet loss, time 60989ms
rtt min/avg/max/mdev = 2.155/8.599/44.475/5.677 ms
300 packets transmitted, 300 received, +1 duplicates, 0% packet loss, time 61030ms
rtt min/avg/max/mdev = 2.158/23.809/300.956/49.969 ms, pipe 2
I would expect packet loss, but got long delays instead.
> also you should consider force the ACK-timing to 450m / Class1
> and forbid retransmission in minstrel
Yes, disabling retransmission would be useful. How would I do that?
Thanks and best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-09-26 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 11:03 Low latency communication over wifi Pavel Machek
2015-09-23 11:21 ` Johannes Berg
2015-09-26 10:24 ` Pavel Machek [this message]
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=20150926102403.GA21555@amd \
--to=pavel@ucw.cz \
--cc=bittorf@bluebottle.com \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--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).