From: Thomas Graf <tgraf@suug.ch>
To: Jesse Gross <jesse@nicira.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH net] tunnels: Don't require remote endpoint or ID during creation.
Date: Sat, 17 Oct 2015 09:45:31 +0200 [thread overview]
Message-ID: <20151017074531.GA13981@pox.localdomain> (raw)
In-Reply-To: <1445038560-85471-1-git-send-email-jesse@nicira.com>
On 10/16/15 at 04:36pm, Jesse Gross wrote:
> Before lightweight tunnels existed, it really didn't make sense to
> create a tunnel that was not fully specified, such as without a
> destination IP address - the resulting packets would go nowhere.
> However, with lightweight tunnels, the opposite is true - it doesn't
> make sense to require this information when it will be provided later
> on by the route. This loosens the requirements for this information.
>
> An alternative would be to allow the relaxed version only when
> COLLECT_METADATA is enabled. However, since there are several
> variations on this theme (such as NBMA tunnels in GRE), just dropping
> the restrictions seems the most consistent across tunnels and with
> the existing configuration.
>
> CC: John Linville <linville@tuxdriver.com>
> Signed-off-by: Jesse Gross <jesse@nicira.com>
I left it like it was for VXLAN with the thought that you had
specifically enable the metadata driven TX but I'm perfectly
fine with this as well.
Signed-off-by: Thomas Graf <tgraf@suug.ch>
next prev parent reply other threads:[~2015-10-17 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 23:36 [PATCH net] tunnels: Don't require remote endpoint or ID during creation Jesse Gross
2015-10-17 7:45 ` Thomas Graf [this message]
2015-10-19 5:44 ` David Miller
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=20151017074531.GA13981@pox.localdomain \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=linville@tuxdriver.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