netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] net: ip: push gso skb forwarding handling down the stack
Date: Wed, 07 May 2014 15:49:40 -0400 (EDT)	[thread overview]
Message-ID: <20140507.154940.261459809114586136.davem@davemloft.net> (raw)
In-Reply-To: <1399294844-7231-1-git-send-email-fw@strlen.de>

From: Florian Westphal <fw@strlen.de>
Date: Mon,  5 May 2014 15:00:42 +0200

> Turns out doing the segmentation in forwarding was not a bright idea,
> there are corner-cases where this has unintended side-effects.
> 
> This patch pushes the segmentation downwards.

Series applied, thanks Florian.

      parent reply	other threads:[~2014-05-07 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 13:00 [PATCH 0/2] net: ip: push gso skb forwarding handling down the stack Florian Westphal
2014-05-05 13:00 ` [PATCH 1/2] " Florian Westphal
2014-05-05 13:00 ` [PATCH 2/2] Revert "net: core: introduce netif_skb_dev_features" Florian Westphal
2014-05-07 19:49 ` 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=20140507.154940.261459809114586136.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    /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).