From: Zhu Yi <yi.zhu@intel.com>
To: Dunc <dunc@lemonia.org>
Cc: Kalle Valo <kalle.valo@iki.fi>,
David Miller <davem@davemloft.net>,
"kaber@trash.net" <kaber@trash.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Network QoS support in applications
Date: Wed, 27 Jan 2010 09:57:51 +0800 [thread overview]
Message-ID: <1264557471.5282.24.camel@debian> (raw)
In-Reply-To: <4B5EF5DF.2070005@lemonia.org>
On Tue, 2010-01-26 at 22:02 +0800, Dunc wrote:
> 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? At this point all
> the good work done in the applications is useless and the network
> admin is going to have to not trust the QoS values and then attempt to
> classify traffic by themselves, so it was all a waste of time.
The QoS values an application sets can be viewed as "hints". It is still
the network admin's choice to use it or not. For example, as a network
admin for an Internet router, you don't want to trust any QoS values
from ingress. But as a smart phone owner, you probably want to trust the
applications running on it. For end users on noncritical devices,
requiring them to do traffic mapping themselves is too much. IMO, having
a way for the applications to specify the traffic priority they _wish_
to have is useful.
Thanks,
-yi
next prev parent reply other threads:[~2010-01-27 1:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 8:27 Network QoS support in applications Kalle Valo
[not found] ` <87k4v5nuej.fsf-ySPBbPOLdCfMApvqMRVM/A@public.gmane.org>
2010-01-26 11:30 ` Patrick McHardy
[not found] ` <4B5ED254.7010104-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
2010-01-26 11:51 ` Kalle Valo
[not found] ` <877hr5nkx0.fsf-ySPBbPOLdCfMApvqMRVM/A@public.gmane.org>
2010-01-26 11:59 ` Patrick McHardy
2010-01-26 12:16 ` David Miller
2010-01-26 12:56 ` Kalle Valo
2010-01-26 13:06 ` David Miller
[not found] ` <20100126.050645.184040277.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-01-26 13:47 ` Kalle Valo
2010-01-26 14:02 ` Dunc
[not found] ` <4B5EF5DF.2070005-9b9L1Hpe0sBAfugRpC6u6w@public.gmane.org>
2010-01-26 14:27 ` Kalle Valo
[not found] ` <87iqaplz5a.fsf-ySPBbPOLdCfMApvqMRVM/A@public.gmane.org>
2010-01-26 21:54 ` Edgar E. Iglesias
2010-01-27 7:11 ` Kalle Valo
2010-01-27 1:57 ` Zhu Yi [this message]
2010-01-27 13:24 ` Benny Amorsen
2010-03-11 19:21 ` Philip A. Prindeville
[not found] ` <4B9942A7.40205-9z15yex7P+UJvtFkdXX2HpqQE7yCjDx5@public.gmane.org>
2010-03-11 19:27 ` David Miller
[not found] ` <20100311.112754.142886660.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-03-11 19:29 ` Philip A. Prindeville
2010-05-19 0:04 ` Philip A. Prindeville
[not found] ` <4BF32B2B.6010202-9z15yex7P+UJvtFkdXX2HpqQE7yCjDx5@public.gmane.org>
2010-05-31 19:30 ` Ben Gardiner
2010-05-31 20:28 ` Philip Prindeville
2010-01-26 14:43 ` Rémi Denis-Courmont
[not found] ` <87wrz5m3cd.fsf-ySPBbPOLdCfMApvqMRVM/A@public.gmane.org>
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-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=1264557471.5282.24.camel@debian \
--to=yi.zhu@intel.com \
--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 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).