From: Harald Welte <laforge@gnumonks.org>
To: "Drewek, Wojciech" <wojciech.drewek@intel.com>
Cc: Marcin Szycik <marcin.szycik@linux.intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"michal.swiatkowski@linux.intel.com"
<michal.swiatkowski@linux.intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pablo@netfilter.org" <pablo@netfilter.org>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"osmocom-net-gprs@lists.osmocom.org"
<osmocom-net-gprs@lists.osmocom.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [PATCH net-next v7 3/7] gtp: Implement GTP echo request
Date: Tue, 22 Feb 2022 21:40:11 +0100 [thread overview]
Message-ID: <YhVKK16JRo3THp7h@nataraja> (raw)
In-Reply-To: <MW4PR11MB5776AA2256C00293FAC07C16FD3B9@MW4PR11MB5776.namprd11.prod.outlook.com>
Hi Wojciech,
On Tue, Feb 22, 2022 at 09:38:08AM +0000, Drewek, Wojciech wrote:
> > I think either the Tx and the Rx ard triggered by / notified to userspace,
> > or you would also do periodic triggering of Tx in the kernel autonomously,
> > and process the responses. But at that point then you also need to think
> > about further consequences, such as counting the number of missed ECHO RESP,
> > and then notify userspace if that condition "N out of M last responses missed".
> >
>
> I thought that with the GTP device created from ip link, userspace
> would be unable to receive Echo Response (similar to Echo Request).
> If it's not the case than I will get rid of handling Echo Response in the
> next version.
Well, userspace cannot 'receive' the ECHO response through the UDP socket as
the UDP socket is hidden in the kernel. I was thinking of the same mechanism
you introduce for transmit: You can trigger the Tx of GTP ECHO REQ via netlink,
so why shouldn't you receive a notifiation about its completion also via netlink?
Just don't think of it as sending an ECHO REQ via netlink, but triggering the tx
and acknowledging the completion/reception of a related response.
One of the advantages of the existing mechanism via 'socket is held in userspace'
is that we don't have to jump through any such hoops or invent strange interfaces:
The process can just send and receive the messages as usual via UDP socket related
syscalls.
--
- 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:[~2022-02-22 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 10:14 [PATCH net-next v7 0/7] ice: GTP support in switchdev Marcin Szycik
2022-02-21 10:14 ` [PATCH net-next v7 1/7] gtp: Allow to create GTP device without FDs Marcin Szycik
2022-02-21 10:14 ` [PATCH net-next v7 2/7] gtp: Implement GTP echo response Marcin Szycik
2022-02-21 10:14 ` [PATCH net-next v7 3/7] gtp: Implement GTP echo request Marcin Szycik
2022-02-22 6:32 ` Harald Welte
2022-02-22 9:38 ` Drewek, Wojciech
2022-02-22 20:40 ` Harald Welte [this message]
2022-02-22 21:49 ` Drewek, Wojciech
2022-02-21 10:14 ` [PATCH net-next v7 4/7] net/sched: Allow flower to match on GTP options Marcin Szycik
2022-02-21 10:14 ` [PATCH net-next v7 5/7] gtp: Add support for checking GTP device type Marcin Szycik
2022-02-21 10:14 ` [PATCH net-next v7 6/7] ice: Fix FV offset searching Marcin Szycik
2022-02-21 10:14 ` [PATCH net-next v7 7/7] ice: Support GTP-U and GTP-C offload in switchdev Marcin Szycik
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=YhVKK16JRo3THp7h@nataraja \
--to=laforge@gnumonks.org \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pablo@netfilter.org \
--cc=wojciech.drewek@intel.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).