From: Olaf van der Spek <olafvdspek@gmail.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Network QoS support in applications
Date: Wed, 27 Jan 2010 17:18:05 +0100 [thread overview]
Message-ID: <b2cc26e41001270818hfa9a533le4aa45a5f2f62eb8@mail.gmail.com> (raw)
In-Reply-To: <87k4v5nuej.fsf@purkki.valot.fi>
On Tue, Jan 26, 2010 at 9:27 AM, Kalle Valo <kalle.valo@iki.fi> wrote:
> I would like to clear up all this by and I'm willing to write a
> document for application developers about network QoS. But I need help
> to understand what's the proper way to mark different QoS
> prioritities.
Maybe it shouldn't be done by applications, unless the streams of an
app use different priorities.
It might be useful to look at configuration of networked apps in a
broader sense, including stuff like to what IP addresses and ports an
app should bind. Maybe even to what Unix sockets or other transports.
Being able to configure this in one central place is way easier then
having to dive into the conf file of each individual application.
In this central place the QoS stuff could be configured too.
As this doesn't require application support, it's probably easier to
implement. It also provides more flexibility and maybe even more
security.
Olaf
next prev parent reply other threads:[~2010-01-27 16:18 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
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 [this message]
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=b2cc26e41001270818hfa9a533le4aa45a5f2f62eb8@mail.gmail.com \
--to=olafvdspek@gmail.com \
--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.