All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Dan Williams <dcbw@redhat.com>
Cc: Greg Oliver <oliver.greg@gmail.com>,
	David Acker <dacker@roinet.com>,
	linux-wireless@vger.kernel.org, patrik.flykt@nokia.com
Subject: Re: WMM classification guideline for applications?
Date: Fri, 04 Dec 2009 23:01:43 +0200	[thread overview]
Message-ID: <87vdgm4fns.fsf@purkki.valot.fi> (raw)
In-Reply-To: <1259954135.27022.6.camel@localhost.localdomain> (Dan Williams's message of "Fri\, 04 Dec 2009 11\:15\:35 -0800")

Dan Williams <dcbw@redhat.com> writes:

> On Fri, 2009-12-04 at 10:56 -0600, Greg Oliver wrote:
>
>> I do nto mean to be negative, but how can vlan based priority mapping
>> be anything but "going in reverse" by today's QoS standards?  The
>> whole point of packet marking is to alleviate the "this port is better
>> than that port", so traffic from any port can be made equal to that of
>> another..  Port (vlan/subnet/interface, etc) agnostic...  This would
>> seem like a regression to me...  All of the major router/switch
>> vendors provide mappings between these techniques already for this
>> reason.  Hopefully, they will not be needed much longer.
>
> Also, I think that unless it's a simple as a setsockopt() or some
> one-call method like that, app writers aren't really going to use it.

Exactly. It needs to be so simple that application developers can just
copy paste it to their code without a second thought. Remember we (as
in community) want even proprietary applications like skype to support
this.

And this method, whatever it will be, should be universal so that it
can be used with different technologies: Wi-Fi, Wimax, cellular data
and whatnot. Otherwise it doesn't make any sense, usually applications
don't care over which technology the packets are transmitted.

-- 
Kalle Valo

  parent reply	other threads:[~2009-12-04 21:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 14:02 WMM classification guideline for applications? Kalle Valo
2009-12-04 15:14 ` David Acker
2009-12-04 15:24   ` Kalle Valo
2009-12-04 16:08     ` David Acker
2009-12-04 16:56       ` Greg Oliver
2009-12-04 19:15         ` Dan Williams
2009-12-04 20:01           ` David Acker
2009-12-07 15:11             ` Kalle Valo
2009-12-04 21:01           ` Kalle Valo [this message]
2009-12-06 10:46       ` Johannes Berg
2009-12-06 18:10         ` David Acker
2009-12-06 18:32           ` Johannes Berg
2009-12-07  1:34             ` David Acker
2009-12-06 10:57 ` Johannes Berg
2009-12-07 15:50   ` Kalle Valo

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=87vdgm4fns.fsf@purkki.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=dacker@roinet.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=oliver.greg@gmail.com \
    --cc=patrik.flykt@nokia.com \
    /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.