[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54AB303E.3000601@gmail.com>
Date: Mon, 05 Jan 2015 16:45:50 -0800
From: John Fastabend <john.fastabend@...il.com>
To: Thomas Graf <tgraf@...g.ch>
CC: sfeldma@...il.com, jiri@...nulli.us, jhs@...atatu.com,
simon.horman@...ronome.com, netdev@...r.kernel.org,
davem@...emloft.net, andy@...yhouse.net
Subject: Re: [net-next PATCH v1 01/11] net: flow_table: create interface for
hw match/action tables
[...]
>>> +/**
>>> + * @struct net_flow_field_ref
>>> + * @brief uniquely identify field as header:field tuple
>>> + */
>>> +struct net_flow_field_ref {
>>> + int instance;
>>> + int header;
>>> + int field;
>>> + int mask_type;
>>> + int type;
>>> + union { /* Are these all the required data types */
>>> + __u8 value_u8;
>>> + __u16 value_u16;
>>> + __u32 value_u32;
>>> + __u64 value_u64;
>>> + };
>>> + union { /* Are these all the required data types */
>>> + __u8 mask_u8;
>>> + __u16 mask_u16;
>>> + __u32 mask_u32;
>>> + __u64 mask_u64;
>>> + };
>>> +};
>>
>> Does it make sense to write this as follows?
>
> Yes. I'll make this update it helps make it clear value/mask pairs are
> needed.
>
>>
>> union {
>> struct {
>> __u8 value_u8;
>> __u8 mask_u8;
>> };
>> struct {
>> __u16 value_u16;
>> __u16 mask_u16;
>> };
>> ...
>> };
Another thought is to pull this entirely out of the structure and hide
it from the UAPI so we can add more value/mask types as needed without
having to spin versions of net_flow_field_ref. On the other hand I've
been able to fit all my fields in these types so far and I can't think
of any additions we need at the moment.
>>
>>> +#define NET_FLOW_TABLE_EGRESS_ROOT 1
>>> +#define NET_FLOW_TABLE_INGRESS_ROOT 2
>>
>> Tab/space mix.
>>
>
[...]
--
John Fastabend Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists