linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Machek <pavel@ucw.cz>, 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: Mon, 28 Sep 2015 09:41:43 +0200	[thread overview]
Message-ID: <1443426103.2401.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20150926102403.GA21555@amd>

On Sat, 2015-09-26 at 12:24 +0200, Pavel Machek wrote:
> 
> 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.

Correct. But it won't *drop* packets, it just increases the chances of
getting medium access.

> > # 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

Yes.

> 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.

See above :)

> > 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?
> 
It won't work on Intel devices though since they don't use
minstrel(_ht)

johannes

  reply	other threads:[~2015-09-28  7:41 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
2015-09-28  7:41     ` Johannes Berg [this message]
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=1443426103.2401.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=bittorf@bluebottle.com \
    --cc=jirislaby@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mickflemm@gmail.com \
    --cc=pavel@ucw.cz \
    /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).