linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: QoS frames in AP mode?
Date: Tue, 27 Dec 2011 22:54:35 +0200	[thread overview]
Message-ID: <20111227205435.GA31878@w1.fi> (raw)
In-Reply-To: <1324024068.3429.0.camel@jlt3.sipsolutions.net>

On Fri, Dec 16, 2011 at 09:27:48AM +0100, Johannes Berg wrote:
> On Fri, 2011-12-16 at 09:14 +0100, Helmut Schaa wrote:
> > On Thu, Dec 15, 2011 at 6:00 PM, Johannes Berg
> > <johannes@sipsolutions.net> wrote:
> > 
> > >>         /* skb->priority values from 256->263 are magic values to
> > >>          * directly indicate a specific 802.1d priority.  This is used
> > >>          * to allow 802.1d priority to be passed directly in from VLAN
> > >>          * tags, etc.
> > >>          */
> > >>         if (skb->priority >= 256 && skb->priority <= 263)
> > >>                 return skb->priority - 256;
> > 
> > Is this code still valid? I haven't found a reference in the 802.1q code :(
> 
> I always thought you'd use like iptables to set it to the right value,
> but I have no idea.

Yes, if my memory serves me right, this was indeed the original reason
for this code (from almost ten years ago... ;-). It was used in some
interesting combination of iptables and tc rules.

-- 
Jouni Malinen                                            PGP id EFC895FA

      reply	other threads:[~2011-12-27 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 16:30 QoS frames in AP mode? Helmut Schaa
2011-12-15 17:00 ` Johannes Berg
2011-12-15 21:08   ` Helmut Schaa
2011-12-16  8:14   ` Helmut Schaa
2011-12-16  8:27     ` Johannes Berg
2011-12-27 20:54       ` Jouni Malinen [this message]

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=20111227205435.GA31878@w1.fi \
    --to=j@w1.fi \
    --cc=helmut.schaa@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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).