netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tparkin@katalix.com
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org, jchapman@katalix.com
Subject: Re: [PATCH] l2tp: avoid checksum offload for fragmented packets
Date: Tue, 11 Jun 2013 01:16:15 -0700 (PDT)	[thread overview]
Message-ID: <20130611.011615.941255845283559918.davem@davemloft.net> (raw)
In-Reply-To: <20130611080038.GA2496@raven>

From: Tom Parkin <tparkin@katalix.com>
Date: Tue, 11 Jun 2013 09:00:38 +0100

> Dave -- could you give me a steer?  Are you happy to keep this kind of
> calculation in the transport layer, or should I look to push something
> generic into the IP code?

I think it's an IP layer issue, so should be handled there.

Thanks.

      reply	other threads:[~2013-06-11  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  7:49 [PATCH] l2tp: avoid checksum offload for fragmented packets Tom Parkin
2013-06-03  7:49 ` Tom Parkin
2013-06-03 14:44   ` Ben Hutchings
2013-06-05  9:41     ` Tom Parkin
2013-06-05 12:57       ` Ben Hutchings
2013-06-11  8:00         ` Tom Parkin
2013-06-11  8:16           ` David Miller [this message]

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=20130611.011615.941255845283559918.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhutchings@solarflare.com \
    --cc=jchapman@katalix.com \
    --cc=netdev@vger.kernel.org \
    --cc=tparkin@katalix.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).