From: Rick Jones <rick.jones2@hpe.com>
To: Mahesh Bandewar <mahesh@bandewar.net>, netdev <netdev@vger.kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Mahesh Bandewar <maheshb@google.com>
Subject: Re: [PATCH next 3/3] ipvlan: Introduce l3s mode
Date: Fri, 9 Sep 2016 15:07:32 -0700 [thread overview]
Message-ID: <e5cc5f33-9a78-cc0f-9244-9a3f7ed4876f@hpe.com> (raw)
In-Reply-To: <1473458010-18571-1-git-send-email-mahesh@bandewar.net>
On 09/09/2016 02:53 PM, Mahesh Bandewar wrote:
> @@ -48,6 +48,11 @@ master device for the L2 processing and routing from that instance will be
> used before packets are queued on the outbound device. In this mode the slaves
> will not receive nor can send multicast / broadcast traffic.
>
> +4.3 L3S mode:
> + This is very similar to the L3 mode except that iptables conn-tracking
> +works in this mode and that is why L3-symsetric (L3s) from iptables perspective.
> +This will have slightly less performance but that shouldn't matter since you
> +are choosing this mode over plain-L3 mode to make conn-tracking work.
What is that first sentence trying to say? It appears to be incomplete,
and is that supposed to be "L3-symmetric?"
happy benchmarking,
rick jones
next prev parent reply other threads:[~2016-09-09 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 21:53 [PATCH next 3/3] ipvlan: Introduce l3s mode Mahesh Bandewar
2016-09-09 22:07 ` Rick Jones [this message]
2016-09-09 22:17 ` Mahesh Bandewar (महेश बंडेवार)
2016-09-09 22:26 ` David Ahern
2016-09-09 22:46 ` Mahesh Bandewar (महेश बंडेवार)
2016-09-10 16:25 ` David Ahern
2016-09-10 18:11 ` David Miller
2016-09-10 18:48 ` Mahesh Bandewar (महेश बंडेवार)
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=e5cc5f33-9a78-cc0f-9244-9a3f7ed4876f@hpe.com \
--to=rick.jones2@hpe.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--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).