From: Govindarajulu Varadarajan <_govind@gmx.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: Govindarajulu Varadarajan <_govind@gmx.com>,
davem@davemloft.net, netdev@vger.kernel.org, ssujith@cisco.com,
gvaradar@cisco.com, benve@cisco.com, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 1/8] flow_keys: Record IP layer protocol in skb_flow_dissect()
Date: Tue, 10 Jun 2014 19:38:00 +0530 (IST) [thread overview]
Message-ID: <alpine.LNX.2.03.1406101923050.2499@ws.cisco> (raw)
In-Reply-To: <539703F5.8030707@redhat.com>
On Tue, 10 Jun 2014, Daniel Borkmann wrote:
>> diff --git a/include/net/flow_keys.h b/include/net/flow_keys.h
>> index 7e64bd8..fbefdca 100644
>> --- a/include/net/flow_keys.h
>> +++ b/include/net/flow_keys.h
>> @@ -1,6 +1,19 @@
>> #ifndef _NET_FLOW_KEYS_H
>> #define _NET_FLOW_KEYS_H
>>
>> +/* struct flow_keys:
>> + * @src: source ip address in case of IPv4
>> + * For IPv6 it contains 32bit hash of src address
>> + * @dst: destination ip address in case of IPv4
>> + * For IPv6 it contains 32bit hash of dst address
>> + * @ports: port numbers of Transport header
>> + * port16[0]: src port number
>> + * port16[1]: dst port number
>> + * @thoff: Transport header offset
>> + * @n_proto: Network header protocol (eg. IPv4/IPv6)
>> + * @ip_proto: Transport header protocol (eg. TCP/UDP)
>> + * All the members, except thoff, are in network byte order.
>> + */
>> struct flow_keys {
>> /* (src,dst) must be grouped, in the same way than in IP header */
>> __be32 src;
>> @@ -10,6 +23,7 @@ struct flow_keys {
>> __be16 port16[2];
>> };
>> u16 thoff;
>> + u16 n_proto;
>> u8 ip_proto;
>> };
>>
>> diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h
>> index 624f985..a3cfb8e 100644
>> --- a/include/net/sch_generic.h
>> +++ b/include/net/sch_generic.h
>> @@ -231,7 +231,7 @@ struct qdisc_skb_cb {
>> unsigned int pkt_len;
>> u16 slave_dev_queue_mapping;
>> u16 _pad;
>> - unsigned char data[20];
>> + unsigned char data[24];
>
> I'm wondering if this is actually needed. We add an extra
> u16 n_proto into the flow_keys *just* to determine IPv4/v6
> while if it finds anything else than this the dissector
> returns false anyway w/o filling out the flow keys structure.
> Plus, in case of IPv6 you'll have a hashed/folded src/dst
> addr anyway.
>
determining IPv4/IPv6 is important because this can be used in dissecting flow
in Accelerated RFS. Adaptor does not support IPv6 filters. Since Accelerated
RFS is supported for IPV6, using skb_flow_dissect will return true with non-zero
values in src/dst for IPv6.
If I am going to write separate function for getting IP address and port
numbers, its definition is going to be somewhat same as skb_flow_dissect.
Why not improve whats already written and reuse it?
Is there any significant downside of adding u16 n_proto and increasing
size of qdisc_skb_cb by 4 bytes?
Thanks
Govind
>> };
>>
>> static inline void qdisc_cb_private_validate(const struct sk_buff *skb,
>> int sz)
>> diff --git a/net/core/flow_dissector.c b/net/core/flow_dissector.c
>> index 107ed12..c2b53c1 100644
>> --- a/net/core/flow_dissector.c
>> +++ b/net/core/flow_dissector.c
>> @@ -175,6 +175,7 @@ ipv6:
>> break;
>> }
>>
>> + flow->n_proto = proto;
>> flow->ip_proto = ip_proto;
>> flow->ports = skb_flow_get_ports(skb, nhoff, ip_proto);
>> flow->thoff = (u16) nhoff;
>>
>
next prev parent reply other threads:[~2014-06-10 14:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 18:32 [PATCH net-next 0/8] enic updates Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 1/8] flow_keys: Record IP layer protocol in skb_flow_dissect() Govindarajulu Varadarajan
2014-06-10 13:11 ` Daniel Borkmann
2014-06-10 14:08 ` Govindarajulu Varadarajan [this message]
2014-06-10 14:26 ` Eric Dumazet
2014-06-11 22:06 ` David Miller
2014-06-11 22:08 ` David Miller
2014-06-12 5:38 ` Govindarajulu Varadarajan
2014-06-19 18:06 ` Chema Gonzalez
2014-06-19 18:52 ` Govindarajulu Varadarajan
2014-06-24 5:29 ` Yinghai Lu
2014-06-26 6:34 ` Govindarajulu Varadarajan
2014-09-18 14:18 ` Or Gerlitz
2014-09-18 14:38 ` Eric Dumazet
2014-09-18 15:02 ` [PATCH net] net: sched: shrink struct qdisc_skb_cb to 28 bytes Eric Dumazet
2014-09-18 16:26 ` Stephen Hemminger
2014-09-18 16:32 ` Eric Dumazet
2014-09-18 18:00 ` Eric Dumazet
2014-09-18 18:07 ` Joe Perches
2014-09-18 19:14 ` Eric Dumazet
2014-09-18 19:31 ` Joe Perches
2014-09-18 20:31 ` Eric Dumazet
2014-09-18 21:28 ` Or Gerlitz
2014-09-18 22:29 ` [net] " Doug Ledford
2014-09-19 12:07 ` Or Gerlitz
2014-09-22 18:38 ` David Miller
2014-09-22 18:22 ` [PATCH net] " David Miller
2014-06-09 18:32 ` [PATCH net-next 2/8] enic: fix return value in _vnic_dev_cmd Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 3/8] enic: devcmd for adding IP 5 tuple hardware filters Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 4/8] enic: alloc/free rx_cpu_rmap Govindarajulu Varadarajan
2014-06-09 18:44 ` Sergei Shtylyov
2014-06-10 13:52 ` Govindarajulu Varadarajan
2014-06-10 15:00 ` Sergei Shtylyov
2014-06-09 18:32 ` [PATCH net-next 5/8] enic: Add Accelerated RFS support Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 6/8] enic: fix lockdep around devcmd_lock Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 7/8] enic: add low latency socket busy_poll support Govindarajulu Varadarajan
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=alpine.LNX.2.03.1406101923050.2499@ws.cisco \
--to=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=gvaradar@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=ssujith@cisco.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;
as well as URLs for NNTP newsgroup(s).