From: Harald Welte <laforge@gnumonks.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: netdev@vger.kernel.org, osmocom-net-gprs@lists.osmocom.org,
Gabriel Ganne <gabriel.ganne@6wind.com>,
kuba@kernel.org, davem@davemloft.net, pablo@netfilter.org
Subject: Re: [PATCH net-next v2] gtp: add notification mechanism
Date: Wed, 26 Aug 2020 20:52:02 +0200 [thread overview]
Message-ID: <20200826185202.GZ3739@nataraja> (raw)
In-Reply-To: <bd834ad7-b06e-69f0-40a6-5f4a21a1eba2@6wind.com>
Hi Nicolas,
On Wed, Aug 26, 2020 at 09:47:54AM +0200, Nicolas Dichtel wrote:
> > Sending (unsolicited) notifications about all of those seems quite heavyweight to me.
>
> There is no 'unsolicited' notifications with this patch. Notifications are sent
> only if a userspace application has subscribed to the gtp mcast group.
> ip routes or conntrack entries are notified in the same way and there could a
> lot of them also (more than 100k conntrack entries for example).
Ok, thanks for reminding me of that. However, even if those events are
not sent/multicasted, it still looks like the proposed patch is
unconditionally allocating a netlink message and filling it with
information about the PDP. That alone looks like adding significant
overhead to every user - even the majority of current use cases where
nobody is listening/subscribing to that multicast group.
Wouldn't it make sense to only allocate + fill those messages if we
actually knew a subscriber existed?
--
- 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-26 18:52 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
2020-08-26 7:47 ` Nicolas Dichtel
2020-08-26 18:52 ` Harald Welte [this message]
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=20200826185202.GZ3739@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