All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Tom Herbert <tom@herbertland.com>
Cc: Saeed Mahameed <saeedm@dev.mellanox.co.il>,
	Saeed Mahameed <saeedm@mellanox.com>,
	"David S. Miller" <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [pull request][net-next 0/3] Mellanox, mlx5 GRE tunnel offloads
Date: Tue, 05 Sep 2017 13:14:10 +0200	[thread overview]
Message-ID: <87r2vls8hp.fsf@stressinduktion.org> (raw)
In-Reply-To: <CALx6S34aDER1Gzpcw+p7+yr91mjiixCh6gnawKSxy7zhVQz+6Q@mail.gmail.com> (Tom Herbert's message of "Mon, 4 Sep 2017 11:56:00 -0700")

Tom Herbert <tom@herbertland.com> writes:

> There is absolutely no requirement in IP that packets are delivered in
> order-- there never has been and there never will be! If the ULP, like
> Ethernet encapsulation, requires in order deliver then it needs to
> implement that itself like TCP, GRE, and other protocols ensure that
> with sequence numbers and reassembly. All of these hoops we do make
> sure that packets always follow the same path and are always in order
> are done for benefit of middlebox devices like stateful firewalls that
> have force us to adopt their concept of network architecture-- in the
> long run this is self-defeating and kills our ability to innovate.
>
> I'm not saying that we shouldn't consider legacy devices, but we
> should scrutinize new development or solutions that perpetuate
> incorrect design or bad assumptions.

So configure RSS per port and ensure no fragments are send to those
ports. This is possible and rather easy to do. It solves the problem
with legacy software and it spreads out packets for your applications.

It is not perfect but it is working and solves both problems.

Bye,
Hannes

  reply	other threads:[~2017-09-05 11:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 23:04 [pull request][net-next 0/3] Mellanox, mlx5 GRE tunnel offloads Saeed Mahameed
2017-08-30 23:04 ` [net-next 1/3] net/mlx5e: Use IP version matching to classify IP traffic Saeed Mahameed
2017-08-30 23:04 ` [net-next 2/3] net/mlx5e: Support TSO and TX checksum offloads for GRE tunnels Saeed Mahameed
2017-08-30 23:04 ` [net-next 3/3] net/mlx5e: Support RSS for GRE tunneled packets Saeed Mahameed
2017-08-31  5:15 ` [pull request][net-next 0/3] Mellanox, mlx5 GRE tunnel offloads David Miller
2017-08-31 13:51 ` Hannes Frederic Sowa
2017-09-02 23:01   ` Saeed Mahameed
2017-09-03  1:32     ` Hannes Frederic Sowa
2017-09-03  1:37       ` Tom Herbert
2017-09-03  4:11         ` Saeed Mahameed
2017-09-03 15:43           ` Tom Herbert
2017-09-03 16:17             ` Or Gerlitz
2017-09-03 16:45               ` Tom Herbert
2017-09-03 18:58                 ` Or Gerlitz
2017-09-04 13:50             ` Hannes Frederic Sowa
2017-09-04 16:15               ` Tom Herbert
2017-09-04 16:52                 ` Hannes Frederic Sowa
2017-09-04 17:11                   ` Tom Herbert
2017-09-04 17:57                     ` Hannes Frederic Sowa
2017-09-04 18:56                       ` Tom Herbert
2017-09-05 11:14                         ` Hannes Frederic Sowa [this message]
2017-09-05 16:02                           ` Tom Herbert
2017-09-05 19:20                             ` Hannes Frederic Sowa
2017-09-05 21:13                               ` Tom Herbert
2017-09-06  3:06                                 ` Alexander Duyck
2017-09-06 16:17                                   ` Tom Herbert
2017-09-06 17:43                                     ` Alexander Duyck
2017-09-06 19:01                                       ` Tom Herbert
2017-09-03  4:07       ` Saeed Mahameed
2017-09-04  9:37         ` Hannes Frederic Sowa

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=87r2vls8hp.fsf@stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@dev.mellanox.co.il \
    --cc=saeedm@mellanox.com \
    --cc=tom@herbertland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.