From: Ben Greear <greearb@candelatech.com>
To: Louis Croisez <louis.croisez@gmail.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] About support of 802.1p standard into 2.6 linux Bridge code
Date: Thu, 01 Mar 2007 09:09:10 -0800 [thread overview]
Message-ID: <45E708B6.5070800@candelatech.com> (raw)
In-Reply-To: <34d8b2fe0703010109r2f881419wbae1f2c8869e6252@mail.gmail.com>
Louis Croisez wrote:
> Ok, thx.
> Is there any netfilter patch or code available to be able to filter
> frames on base of such QoS parameter?
There is probably a way to filter based off on the skb->priority, but I
have never tried.
Ben
>
> On 2/28/07, *Ben Greear* < greearb@candelatech.com
> <mailto:greearb@candelatech.com>> wrote:
>
> Louis Croisez wrote:
> > Hello,
> > i would like to know if the 802.1p (QoS for Ethernet frames)
> standard
> > is implemented into last 2.6 kernel Bridging code?
> > Cheers,
> > Louis.
> It's implemented in the VLAN code, at least as far as being able
> to map
> a socket priority to a vlan priority. There
> is no special queue handling based on the priority bits at this
> time, at
> least in vlan code.
>
> Ben
>
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Bridge mailing list
> > Bridge@lists.osdl.org <mailto:Bridge@lists.osdl.org>
> > https://lists.osdl.org/mailman/listinfo/bridge
> >
>
>
> --
> Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>
> Candela Technologies Inc http://www.candelatech.com
>
>
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2007-03-01 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34d8b2fe0702270811h5098894aia299857618e8dde@mail.gmail.com>
2007-02-28 14:25 ` [Bridge] About support of 802.1p standard into 2.6 linux Bridge code Louis Croisez
2007-02-28 17:58 ` Ben Greear
2007-03-01 9:09 ` Louis Croisez
2007-03-01 17:09 ` Ben Greear [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=45E708B6.5070800@candelatech.com \
--to=greearb@candelatech.com \
--cc=bridge@lists.osdl.org \
--cc=louis.croisez@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox