netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Gross <jesse@nicira.com>
To: Tom Herbert <therbert@google.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 3/3] vxlan: Remote checksum offload
Date: Mon, 24 Nov 2014 17:06:06 -0800	[thread overview]
Message-ID: <CAEP_g=9_6Rq9Ssr_2q4MKfSDxeL23rbExP5ziHbeCL0Nx-VTvw@mail.gmail.com> (raw)
In-Reply-To: <1416873150-12260-4-git-send-email-therbert@google.com>

On Mon, Nov 24, 2014 at 3:52 PM, Tom Herbert <therbert@google.com> wrote:
> Add support for remote checksum offload in VXLAN. This commandeers a
> reserved bit to indicate that RCO is being done, and uses the low order
> reserved eight bits of the VNI to hold the start and offset values in a
> compressed manner.

Why do you think that this is OK for you to do? It's clear that there
is no consensus for this (and in fact there are other proposals that
use that bit in a different way).

  reply	other threads:[~2014-11-25  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 23:52 [PATCH net-next 0/3] net: Remote checksum offload for VXLAN Tom Herbert
2014-11-24 23:52 ` [PATCH net-next 1/3] net: Add remcsum_adjust as common function for remote checksum offload Tom Herbert
2014-11-24 23:52 ` [PATCH net-next 2/3] gue: Call remcsum_adjust Tom Herbert
2014-11-24 23:52 ` [PATCH net-next 3/3] vxlan: Remote checksum offload Tom Herbert
2014-11-25  1:06   ` Jesse Gross [this message]
2014-11-25  2:50     ` Tom Herbert
2014-11-25 18:54       ` Jesse Gross
2014-11-25 18:50 ` [PATCH net-next 0/3] net: Remote checksum offload for VXLAN David Miller

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='CAEP_g=9_6Rq9Ssr_2q4MKfSDxeL23rbExP5ziHbeCL0Nx-VTvw@mail.gmail.com' \
    --to=jesse@nicira.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.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).