From: James Chapman <jchapman@katalix.com>
To: "R. Parameswaran" <parameswaran.r7@gmail.com>
Cc: David Miller <davem@davemloft.net>,
kleptog@svana.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, nprachan@brocade.com,
rshearma@brocade.com, dfawcus@brocade.com,
stephen@networkplumber.org, acme@redhat.com,
lboccass@brocade.com
Subject: Re: [PATCH net v2] L2TP:Adjust intf MTU,factor underlay L3,overlay L2
Date: Thu, 29 Sep 2016 16:39:21 +0100 [thread overview]
Message-ID: <57ED35A9.7080604@katalix.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1609281857050.17015@duvvury48.eng.vyatta.net>
On 29/09/16 03:36, R. Parameswaran wrote:
> I agree that something like 2. below would be needed in the long run (it
> will need some effort and redesign -e.g. how do I lookup the parent tunnel
> from the socket when receiving a PMTU update, existing pointer chain runs
> from tunnel to socket).
>> 2) Add code to handle PMTU events that land on the UDP tunnel
>> socket.
Another function pointer could be added to struct udp_sock, similar to
encap_rcv, such that the pmtu event could be handled by the UDP encap
protocol implementation.
James
next prev parent reply other threads:[~2016-09-29 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 20:52 [PATCH net v2] L2TP:Adjust intf MTU,factor underlay L3,overlay L2 R. Parameswaran
2016-09-27 7:31 ` David Miller
2016-09-27 19:17 ` R. Parameswaran
2016-09-28 7:48 ` David Miller
2016-09-29 2:36 ` R. Parameswaran
2016-09-29 12:21 ` Jiri Benc
2016-09-29 15:39 ` James Chapman [this message]
2016-09-29 15:18 ` James Chapman
2016-09-30 2:39 ` R. Parameswaran
2016-10-01 16:50 ` James Chapman
2016-10-04 3:12 ` R. Parameswaran
2016-10-04 7:53 ` James Chapman
[not found] ` <CAGeBGG7AS1JZYHC6T5_H6vY4wfptUtPzO=+kdCcUzJGXA0m6_A@mail.gmail.com>
2016-10-11 7:47 ` James Chapman
2016-10-17 4:05 ` [RFC PATCH v3 1/2] " R. Parameswaran
2016-10-17 5:20 ` [RFC PATCH v3 2/2] " R. Parameswaran
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=57ED35A9.7080604@katalix.com \
--to=jchapman@katalix.com \
--cc=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=dfawcus@brocade.com \
--cc=kleptog@svana.org \
--cc=lboccass@brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nprachan@brocade.com \
--cc=parameswaran.r7@gmail.com \
--cc=rshearma@brocade.com \
--cc=stephen@networkplumber.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 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.