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, hannes@stressinduktion.org,
	edumazet@google.com, herbert@gondor.apana.org.au
Subject: Re: [PATCH -next] net: preserve geometry of fragment sizes when forwarding
Date: Mon, 18 May 2015 16:28:54 -0400 (EDT)	[thread overview]
Message-ID: <20150518.162854.1116793790405432801.davem@davemloft.net> (raw)
In-Reply-To: <20150518200637.GB20709@breakpoint.cc>

From: Florian Westphal <fw@strlen.de>
Date: Mon, 18 May 2015 22:06:37 +0200

> So, please please re-evaluate your stance on any of the previous
> attempts or tell me how you would provide bridge netfilter with
> the means to transparently forward (refrag) reassembled skbs, without
> breaking PMTUD, in ipv4 and ipv6.

I know you really don't want to do it, but I really want to see
the "GRO'ish" idea implemented to solve all of these problems.

I know it's hard, and you're making it clear here that you'd
rather just pass an mtu argument around or duplicate the entire
ip fragmentation code base into br_netfilter to solve this problem.

But as networking maintainer I'm supposed to tell you "no" when
those kinds of proposals are being made.  Ok?

We have amazing infrastructure for dealing with oddly segmented
packets, such as skb_header_pointer().  So parsing things in
a fragmented SKB should be no problem regardless of where the
split points are.

We could have suitable interfaces for writing to packets as well,
which would be equally fast as direct access unless the SKB is
split in the middle of the object you want to write into.

The only real barrier left is overlapping fragments, and for that I'd
say just that for netfilter we can just trim the edges, just like the
ip_fragment code already does, and adjust the protocol headers
as-needed.

  reply	other threads:[~2015-05-18 20:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 21:04 [PATCH -next] net: preserve geometry of fragment sizes when forwarding Florian Westphal
2015-05-18 19:39 ` David Miller
2015-05-18 20:06   ` Florian Westphal
2015-05-18 20:28     ` David Miller [this message]
2015-05-18 20:40       ` Florian Westphal
2015-05-18 20:55         ` David Miller
2015-05-18 21:33           ` Florian Westphal
2015-05-18 22:50             ` Herbert Xu
2015-05-18 23:02               ` Florian Westphal
2015-05-18 23:20                 ` Herbert Xu
2015-05-18 23:51             ` David Miller
2015-05-19 12:34               ` Florian Westphal
2015-05-19 19:34                 ` Jay Vosburgh

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=20150518.162854.1116793790405432801.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=hannes@stressinduktion.org \
    --cc=herbert@gondor.apana.org.au \
    --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).