From: "John W. Linville" <linville@tuxdriver.com>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jesse@nicira.com,
kernel-team@fb.com
Subject: Re: [PATCH net-next 2/3] geneve: UDP checksum configuration via netlink
Date: Tue, 8 Dec 2015 14:27:04 -0500 [thread overview]
Message-ID: <20151208192704.GG3598@tuxdriver.com> (raw)
In-Reply-To: <1449599238-4094072-3-git-send-email-tom@herbertland.com>
On Tue, Dec 08, 2015 at 10:27:17AM -0800, Tom Herbert wrote:
> Add support to enable and disable UDP checksums via netlink. This is
> similar to how VXLAN and GUE allow this. This includes support for
> enabling the UDP zero checksum (for both TX and RX).
>
> Signed-off-by: Tom Herbert <tom@herbertland.com>
Now I can drop this from my todo list... :-)
Acked-by: John W. Linville <linville@tuxdriver.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2015-12-08 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 18:27 [PATCH net-next 0/3] geneve: Add support for Remote Checksum Offload Tom Herbert
2015-12-08 18:27 ` [PATCH net-next 1/3] rco: Clean up casting errors Tom Herbert
2015-12-08 18:27 ` [PATCH net-next 2/3] geneve: UDP checksum configuration via netlink Tom Herbert
2015-12-08 19:27 ` John W. Linville [this message]
2015-12-08 18:27 ` [PATCH net-next 3/3] geneve: Remote Checksum Offload support Tom Herbert
2015-12-08 19:31 ` John W. Linville
2015-12-08 19:59 ` Tom Herbert
2015-12-08 23:58 ` Jesse Gross
2015-12-09 0:11 ` Tom Herbert
2015-12-09 1:13 ` Jesse Gross
2015-12-09 2:20 ` David Miller
2015-12-08 20:45 ` [PATCH] geneve: fix noderef.cocci warnings kbuild test robot
2015-12-08 20:45 ` [PATCH net-next 3/3] geneve: Remote Checksum Offload support kbuild test robot
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=20151208192704.GG3598@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.