From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Bastian Bittorf <bittorf@bluebottle.com>,
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: Wed, 30 Sep 2015 20:28:42 +0200 [thread overview]
Message-ID: <1443637722.1859.15.camel@sipsolutions.net> (raw)
In-Reply-To: <20150930172440.GA11160@amd>
On Wed, 2015-09-30 at 19:24 +0200, Pavel Machek wrote:
> On Mon 2015-09-28 09:41:43, Johannes Berg wrote:
> > 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.
>
> Increases chances of medium access, but limits number of retries, so
> it should drop sooner, no?
No, assigning VO AC by itself won't (typically) limit the number of
retries.
> This should send the second ping to the priority queue based on -Q,
> but I don't see an effect against one access point.... and it seems to
> work somehow against second one. Good!
>
Well it depends on whether or not your AP supports WMM/QoS to start
with :)
johannes
next prev parent reply other threads:[~2015-09-30 18:28 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
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 [this message]
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=1443637722.1859.15.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).