From: Johannes Berg <johannes@sipsolutions.net>
To: Guy Cohen <guy.cohen@intel.com>
Cc: Jouni Malinen <j@w1.fi>, linux-wireless@vger.kernel.org
Subject: Re: WMM QoS classification with local bridging (bridge_packets=1)
Date: Thu, 10 Jan 2008 00:58:48 +0100 [thread overview]
Message-ID: <1199923128.3861.45.camel@johannes.berg> (raw)
In-Reply-To: <247d6d340801090503k289902afwd9fc22dbb4a1e70b@mail.gmail.com> (sfid-20080109_130401_569599_6C500E5B)
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Hi,
> What do you think is the right way to fix this? Parse the frame in
> deliver_skb and set the protocol to be IP (when IP frame), or leave
> that as is and in classify_1d parse the frame instead of testing the
> protocol field?
Can you explain the spec requirements? I'm mostly ignorant of the
11e/11n specs. It seems like if the TID should be preserved we should do
that regardless of whether the packet is IP/non-IP so neither of these
solutions would work. But maybe that's not what is required?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-01-10 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 13:03 WMM QoS classification with local bridging (bridge_packets=1) Guy Cohen
2008-01-09 23:58 ` Johannes Berg [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=1199923128.3861.45.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=guy.cohen@intel.com \
--cc=j@w1.fi \
--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