From: Harald Welte <laforge@gnumonks.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: davem@davemloft.net, kuba@kernel.org, pablo@netfilter.org,
osmocom-net-gprs@lists.osmocom.org, netdev@vger.kernel.org,
Gabriel Ganne <gabriel.ganne@6wind.com>
Subject: Re: [PATCH net-next v2] gtp: add notification mechanism
Date: Tue, 25 Aug 2020 19:01:09 +0200 [thread overview]
Message-ID: <20200825170109.GH3822842@nataraja> (raw)
In-Reply-To: <20200825155715.24006-1-nicolas.dichtel@6wind.com>
Hi Nicolas,
thanks a lot for your patch.
On Tue, Aug 25, 2020 at 05:57:15PM +0200, Nicolas Dichtel wrote:
> Like all other network functions, let's notify gtp context on creation and
> deletion.
While this may be in-line with typical kernel tunnel device practises, I am not
convinced it is the right way to go for GTP.
Contrary to other tunneling mechansims, GTP doesn't have a 1:1 rlationship between
tunnels and netdev's. You can easily have tens of thousands - or even many more -
PDP contexts (at least one per subscriber) within one "gtp0" netdev. Also, the state
is highly volatile. Every time a subscriber registers/deregisters, goes in or out of
coverage, in or out of airplane mode, etc. those PDP contexts go up and down.
Sending (unsolicited) notifications about all of those seems quite heavyweight to me.
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2020-08-25 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 14:35 [PATCH net-next] gtp: add notification mechnism Nicolas Dichtel
2020-08-25 15:57 ` [PATCH net-next v2] gtp: add notification mechanism Nicolas Dichtel
2020-08-25 17:01 ` Harald Welte [this message]
2020-08-26 7:47 ` Nicolas Dichtel
2020-08-26 18:52 ` Harald Welte
2020-08-26 22:36 ` Nicolas Dichtel
2020-08-27 9:00 ` Harald Welte
2020-08-27 10:25 ` Nicolas Dichtel
2020-08-27 12:19 ` [PATCH net-next v3] " Nicolas Dichtel
2020-08-27 15:05 ` David Miller
2020-08-27 16:37 ` Nicolas Dichtel
2020-08-27 16:44 ` David Miller
2020-08-27 16:45 ` Nicolas Dichtel
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=20200825170109.GH3822842@nataraja \
--to=laforge@gnumonks.org \
--cc=davem@davemloft.net \
--cc=gabriel.ganne@6wind.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pablo@netfilter.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).