From: Jan Ceuleers <jan.ceuleers@computer.org>
To: "Grégoire Baron" <baronchon@n7mm.org>, netdev@vger.kernel.org
Subject: Re: Network protocol (IP,IPv6,...) and TC actions
Date: Tue, 13 Apr 2010 19:31:07 +0200 [thread overview]
Message-ID: <4BC4AA5B.8040901@computer.org> (raw)
In-Reply-To: <20100411190845.GA18383@n7mm.org>
Grégoire Baron wrote:
> As this .protocol member seems to be used at different moments when a
> packet is received, forwared or sent, and could contain something like
> ETH_P_8021Q which isn't a network protocol Id, can we say the struct
> sk_buff .protocol member is guaranteed to contain a network protocol Id
> in the struct sb_buff used in the TC action executions ?
Grégoire,
I suggest that you ask your question on the netdev mailing list (netdev@vger.kernel.org).
Cheers, Jan
next parent reply other threads:[~2010-04-13 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100411190845.GA18383@n7mm.org>
2010-04-13 17:31 ` Jan Ceuleers [this message]
2010-04-16 23:10 ` Network protocol (IP,IPv6,...) and TC actions (ACT_CSUM) Grégoire Baron
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=4BC4AA5B.8040901@computer.org \
--to=jan.ceuleers@computer.org \
--cc=baronchon@n7mm.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 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).