From: Thomas Graf <tgraf@suug.ch>
To: Jesse Gross <jesse@nicira.com>
Cc: Alexei Starovoitov <ast@plumgrid.com>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] vxlan: expose COLLECT_METADATA flag to user space
Date: Wed, 5 Aug 2015 16:39:15 +0200 [thread overview]
Message-ID: <20150805143915.GA3530@pox.localdomain> (raw)
In-Reply-To: <CAEP_g=-7-PkYGdcigXC68nh+nCKHkr=9soYjcQsCx5rOkTQ90Q@mail.gmail.com>
On 08/03/15 at 02:14pm, Jesse Gross wrote:
> On Fri, Jul 31, 2015 at 8:41 AM, Alexei Starovoitov <ast@plumgrid.com> wrote:
> > thanks. I think exposing collect_metadata for vxlan and in the future
> > for other tunnel types is the clean enough way, though the other
> > alternative would be to get rid of collect_metadata flag
> > from the kernel and do it when flowmode flag is set. Thoughts?
>
> This seems like a good idea to me - I'm not sure that flow based
> tunnels are all that useful without metadata collection enabled and
> the fewer interfaces that we have to create for each tunnel type, the
> better.
The use case at hand where the flag is useful if someone is only
doing flow based TX which can be handy if the tunnel id remains
unused.
next prev parent reply other threads:[~2015-08-05 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 3:10 [PATCH net-next] vxlan: expose COLLECT_METADATA flag to user space Alexei Starovoitov
2015-07-31 8:00 ` Thomas Graf
2015-07-31 15:41 ` Alexei Starovoitov
2015-08-03 21:14 ` Jesse Gross
2015-08-05 14:39 ` Thomas Graf [this message]
2015-07-31 22:24 ` 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=20150805143915.GA3530@pox.localdomain \
--to=tgraf@suug.ch \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jesse@nicira.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).