netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC 0/12] Remove UDP Fragmentation Offload support
Date: Wed, 5 Jul 2017 08:52:17 -0700	[thread overview]
Message-ID: <20170705085217.7161b3cb@xeon-e3> (raw)
In-Reply-To: <20170705.160402.80726683432003025.davem@davemloft.net>

On Wed, 05 Jul 2017 16:04:02 +0100 (WEST)
David Miller <davem@davemloft.net> wrote:

> This is an RFC patch series, based upon some discussions with
> various developers, that removes UFO offloading.
> 
> Very few devices support this operation, it's usefullness is
> quesitonable at best, and it adds a non-trivial amount of
> complexity to our data paths.
> 
> Signed-off-by: David S. Miller <davem@davemloft.net>


Agreed, makes sense to me.

      reply	other threads:[~2017-07-05 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 15:04 [PATCH RFC 0/12] Remove UDP Fragmentation Offload support David Miller
2017-07-05 15:52 ` Stephen Hemminger [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=20170705085217.7161b3cb@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=davem@davemloft.net \
    --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).