From: Jiri Benc <jbenc@redhat.com>
To: Pravin Shelar <pshelar@nicira.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net v3] openvswitch: Fix egress tunnel info.
Date: Sat, 24 Oct 2015 12:26:04 +0200 [thread overview]
Message-ID: <20151024122604.45453ac9@griffin> (raw)
In-Reply-To: <CALnjE+p644A-H1Kj3cc2WE_NOwyeU-8A_8bfvjp_ykUxcUmWeg@mail.gmail.com>
On Fri, 23 Oct 2015 12:47:09 -0700, Pravin Shelar wrote:
> This is not complete code. I found couple of issues with it.
That's likely, I didn't test it :-)
> This code does not copy lwtunnel_state state into new dst.
Not sure what state you mean. All the relevant state should be in
struct ip_tunnel_info.
> And it is converting lwtunnel dst into metadata dst.
I did that intentionally. But your comment made me realize that I was
too much focused on the tunnel implementation side. This function,
should it be used outside of ovs, could be called earlier than the skb
is handed to the tunnel. Then we of course need a valid dst->output and
this approach (converting lwtunnel data to metadata_dst) would fail.
This is the same problem we have with IPv6 ndisc replies.
This needs more thinking and is out of scope of what you're trying to
solve. Sorry for the noise. But at least it made me realize that the
ndisc problem (that I still don't have a good solution for) is broader.
Thanks,
Jiri
--
Jiri Benc
prev parent reply other threads:[~2015-10-24 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 1:17 [PATCH net v3] openvswitch: Fix egress tunnel info Pravin B Shelar
2015-10-23 2:39 ` David Miller
2015-10-23 12:17 ` Jiri Benc
2015-10-23 17:30 ` Pravin Shelar
2015-10-23 18:22 ` Jiri Benc
2015-10-23 19:47 ` Pravin Shelar
2015-10-24 10:26 ` Jiri Benc [this message]
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=20151024122604.45453ac9@griffin \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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 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).