From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: shemminger@osdl.org
Cc: davem@redhat.com, hadi@znyx.com, arekm@pld-linux.org,
netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] pkt_cls.h incompatiables
Date: Thu, 22 Jul 2004 20:04:26 -0400 (EDT) [thread overview]
Message-ID: <20040722.200426.99255296.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20040722134522.4e7e0b07@dell_ss3.pdx.osdl.net>
In article <20040722134522.4e7e0b07@dell_ss3.pdx.osdl.net> (at Thu, 22 Jul 2004 13:45:22 -0700), Stephen Hemminger <shemminger@osdl.org> says:
> The recent changes to (6 Jul 04) pkt_cls.h are evil, you can't build a version
> of 'tc' to work unless you know the kernel config!
>
> It has several API problems:
> - API data structures change on kernel config options
> - new fields should be added at the end of a structure to allow
> binary compatibility.
- We cannot add new variable(s) after the last member which is
an variable-length array in effect.
> @@ -229,11 +214,9 @@
>
> short hoff;
> __u32 hmask;
> -#ifdef CONFIG_CLS_U32_PERF
> + struct tc_u32_key keys[0];
> unsigned long rcnt;
> unsigned long rhit;
> -#endif
> - struct tc_u32_key keys[0];
> };
>
> /* Flags */
We cannot do this because keys holds key of variable length.
Solutions are, for example,
to allocate new TCA_U32_xxx for rcnt and rhit,
or,
to rename TCA_U32_SEL to TCA_U32_OLS_SEL and allocate new value for
TCA_U32_SEL.
--yoshfuji
next prev parent reply other threads:[~2004-07-23 0:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200407161544.59342.arekm@pld-linux.org>
[not found] ` <20040716103759.1928c2ae@dell_ss3.pdx.osdl.net>
[not found] ` <200407172357.15832.arekm@pld-linux.org>
2004-07-22 20:45 ` [PATCH] pkt_cls.h incompatiables Stephen Hemminger
2004-07-22 20:53 ` David S. Miller
2004-07-23 0:04 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2004-07-23 14:41 ` Jamal Hadi Salim
2004-07-23 15:00 ` YOSHIFUJI Hideaki / 吉藤英明
2004-07-23 16:21 ` Stephen Hemminger
2004-07-23 20:25 ` Jamal Hadi Salim
2004-07-23 19:57 ` Jamal Hadi Salim
2004-07-23 20:59 ` David S. Miller
2004-07-24 0:49 ` Jamal Hadi Salim
2004-07-24 1:42 ` YOSHIFUJI Hideaki / 吉藤英明
2004-07-24 12:16 ` Jamal Hadi Salim
2004-07-24 13:33 ` jamal
2004-07-25 1:33 ` YOSHIFUJI Hideaki / 吉藤英明
2004-07-25 6:25 ` David S. Miller
2004-07-25 5:28 ` David S. Miller
2004-07-29 11:22 ` jamal
2004-07-29 11:30 ` jamal
2004-07-29 22:54 ` David S. Miller
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=20040722.200426.99255296.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=arekm@pld-linux.org \
--cc=davem@redhat.com \
--cc=hadi@znyx.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).