From: Benny Amorsen <benny+usenet@amorsen.dk>
To: Dunc <dunc@lemonia.org>
Cc: Kalle Valo <kalle.valo@iki.fi>,
David Miller <davem@davemloft.net>,
kaber@trash.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: Network QoS support in applications
Date: Wed, 27 Jan 2010 14:24:28 +0100 [thread overview]
Message-ID: <m3636nd6k3.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <4B5EF5DF.2070005@lemonia.org> (dunc@lemonia.org's message of "Tue, 26 Jan 2010 14:02:07 +0000")
Dunc <dunc@lemonia.org> writes:
> If applications set the QoS values, the who's to stop someone (for
> example) writing a bittorrent client that marks all packets for the
> highest priority as if they were VoIP or something?
Nothing, but nothing stops them from writing a bittorrent client which
does "optimistic ACK" either. Yet noone seems to bother.
Also, bittorrent marked as EF could easily get hit by a "don't queue
voice packets, just drop instead" policy. Late voice packets are useless
and might as well be dropped, but TCP streams like bittorrent react
badly to packet loss.
All in all there is little incentive for people to game the system.
Should it happen anyway, network administrators have plentiful tools for
fixing it, up to and including ip link set dev whatever down.
/Benny
next prev parent reply other threads:[~2010-01-27 13:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 8:27 Network QoS support in applications Kalle Valo
2010-01-26 8:27 ` Kalle Valo
2010-01-26 11:30 ` Patrick McHardy
2010-01-26 11:30 ` Patrick McHardy
2010-01-26 11:51 ` Kalle Valo
2010-01-26 11:51 ` Kalle Valo
2010-01-26 11:59 ` Patrick McHardy
2010-01-26 11:59 ` Patrick McHardy
2010-01-26 12:16 ` David Miller
2010-01-26 12:16 ` David Miller
2010-01-26 12:56 ` Kalle Valo
2010-01-26 13:06 ` David Miller
2010-01-26 13:47 ` Kalle Valo
2010-01-26 13:47 ` Kalle Valo
2010-01-26 14:02 ` Dunc
2010-01-26 14:27 ` Kalle Valo
2010-01-26 14:27 ` Kalle Valo
2010-01-26 21:54 ` Edgar E. Iglesias
2010-01-26 21:54 ` Edgar E. Iglesias
2010-01-27 7:11 ` Kalle Valo
2010-01-27 1:57 ` Zhu Yi
2010-01-27 13:24 ` Benny Amorsen [this message]
2010-03-11 19:21 ` Philip A. Prindeville
2010-03-11 19:27 ` David Miller
2010-03-11 19:27 ` David Miller
2010-03-11 19:29 ` Philip A. Prindeville
2010-03-11 19:29 ` Philip A. Prindeville
2010-05-19 0:04 ` Philip A. Prindeville
2010-05-31 19:30 ` Ben Gardiner
2010-05-31 19:30 ` Ben Gardiner
2010-05-31 20:28 ` Philip Prindeville
2010-01-26 14:43 ` Rémi Denis-Courmont
2010-01-26 14:43 ` Rémi Denis-Courmont
2010-01-26 13:06 ` Henning Rogge
2010-01-26 13:06 ` Henning Rogge
2010-01-27 6:59 ` Kalle Valo
2010-01-26 15:29 ` Steven Blake
2010-01-27 7:03 ` Kalle Valo
2010-01-27 16:18 ` Olaf van der Spek
2010-01-27 16:26 ` Greg Oliver
2010-03-11 18:56 ` Philip A. Prindeville
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=m3636nd6k3.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=davem@davemloft.net \
--cc=dunc@lemonia.org \
--cc=kaber@trash.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.