netdev - [PATCH net-next V1 0/2] Add UDP GRO support for vxlan traffic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1388935422-7331-1-git-send-email-ogerlitz@mellanox.com>
Date:	Sun,  5 Jan 2014 17:23:40 +0200
From:	Or Gerlitz <ogerlitz@...lanox.com>
To:	hkchu@...gle.com, edumazet@...gle.com, herbert@...dor.apana.org.au
Cc:	netdev@...r.kernel.org, davem@...emloft.net, yanb@...lanox.com,
	shlomop@...lanox.com, Or Gerlitz <ogerlitz@...lanox.com>
Subject: [PATCH net-next V1 0/2] Add UDP GRO support for vxlan traffic

Add GRO handlers for UDP, with the intent of being able to coalesce vxlan
packets which encapsulate packets belonging to the same TCP session.

The UDP GRO handler will only attempt to coalesce packets whose
destination port is used as vxlan listening port.

Patches are against net-next a1d4b03a076d95e "Merge branch 'bgmac'" plus 
Jerry's gro-gre patch which adds the gro_find_receive/complete_by_type helpers

Or.

changes from V0:
 - addressed feedback from Dave on the pre-patch
 - added helpers used by the vxlan code to notify the udp gro code 
   which ports are used for vxlan

Or Gerlitz (2):
  net: Pre-step for supporting GRO on vxlan traffic
  net: Add UDP GRO support for vxlan traffic

 drivers/net/vxlan.c    |   13 ++---
 include/net/protocol.h |    3 +
 include/net/vxlan.h    |    6 ++
 net/ipv4/udp_offload.c |  127 ++++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 141 insertions(+), 8 deletions(-)

--
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