[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1388951306.12212.169.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Sun, 05 Jan 2014 11:48:26 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Or Gerlitz <or.gerlitz@...il.com>
Cc: Or Gerlitz <ogerlitz@...lanox.com>, Jerry Chu <hkchu@...gle.com>,
Eric Dumazet <edumazet@...gle.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Yan Burman <yanb@...lanox.com>,
Shlomo Pongratz <shlomop@...lanox.com>
Subject: Re: [PATCH V1 net-next 2/2] net: Add UDP GRO support for vxlan
traffic
On Sun, 2014-01-05 at 21:39 +0200, Or Gerlitz wrote:
> To be accurate here, V1 (this patch) still has RFC aspects -- it
> suggests a solution to the above matter -- the gro udp code exports
> two callbacks which are invoked by the vxlan driver to add/delete udp
> listening port. The callbacks maintain an O(1) accessed array which is
> beeing looked from the fast path to determine if the destination udp
> port of the packet under inspection is a vxlan listening port.
This implementation uses a u8 for 64K ports, I am pretty sure you could
use a bitmap instead so that a UDP forwarding workload do not need to
bring 64KB in cpu caches, but only 8KB.
--
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