[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZJP7NGdQnHs1tVXny19w4mstEaEBi5WEvktZ4MumCfy0w@mail.gmail.com>
Date: Tue, 14 Jan 2014 23:47:17 +0200
From: Or Gerlitz <or.gerlitz@...il.com>
To: Tom Herbert <therbert@...gle.com>
Cc: Or Gerlitz <ogerlitz@...lanox.com>,
David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Jerry Chu <hkchu@...gle.com>,
Eric Dumazet <edumazet@...gle.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Yan Burman <yanb@...lanox.com>,
Shlomo Pongratz <shlomop@...lanox.com>
Subject: Re: [PATCH net-next V4 3/3] net: Add GRO support for vxlan traffic
On Tue, Jan 14, 2014 at 7:59 PM, Tom Herbert <therbert@...gle.com> wrote:
>
> On Tue, Jan 14, 2014 at 8:00 AM, Or Gerlitz <ogerlitz@...lanox.com> wrote:
> > Add GRO handlers for vxlann, by using the UDP GRO infrastructure.
[...]
>
> > /* Notify netdevs that UDP port started listening */
> > -static void vxlan_notify_add_rx_port(struct sock *sk)
> > +static void vxlan_notify_add_rx_port(struct vxlan_sock *vs)
> > {
> > struct net_device *dev;
> > + struct sock *sk = vs->sock->sk;
> > struct net *net = sock_net(sk);
> > sa_family_t sa_family = sk->sk_family;
> > __be16 port = inet_sk(sk)->inet_sport;
> > + int err;
> > +
> > + if (sa_family == AF_INET) {
> Is this necessary? What about support for AF_INET6?
Point taken -- the UDP GRO code for both ipv4 and ipv6 would work the same.
So we can export udp_gro_receive/complete from net/ipv4/udp_offload.c
such that they can be referred from net/ipv6/udp_offload.c
>
> > + err = udp_add_offload(&vs->udp_offloads);
> > + if (err)
> > + pr_warn("vxlan: udp_add_offload failed with status %d\n", err);
> > + }
> >
> > rcu_read_lock();
> > for_each_netdev_rcu(net, dev) {
--
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