From: "Lukas Bartosik [C]" <lbartosik@marvell.com>
To: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
"Narayana Prasad Raju Athreya" <pathreya@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: fix dropping of initial IPsec pkts
Date: Wed, 15 Apr 2020 16:27:57 +0000 [thread overview]
Message-ID: <139b63ab-6ce0-1657-2754-37e1347143bc@marvell.com> (raw)
In-Reply-To: <1586345520-3205-1-git-send-email-lbartosik@marvell.com>
Hi Konstantin,
In this patch I moved the sa_init() before rte_eth_dev_start() in order to avoid dropping
of IPsec pkts when a traffic flows and the ipsec-secgw application is started.
However I remember that during review of event mode patches you mentioned that
moving sa_init() before rte_eth_dev_start() is an issue for one of
the Intel drivers. Is this still the case ?
Thanks,
Lukasz
On 08.04.2020 13:32, Lukasz Bartosik wrote:
> In inline event mode when traffic flows and the ipsec-secgw
> app is started then for short period of time IPsec packets
> arrive at application without being decrypted and are dropped
> by the application. This happens because eth ports are started
> before creation of inline sessions and IPsec flows. This fix
> rearranges the code in such a way that eth ports are always
> started after creation of inline sessions and IPsec flows.
>
> Change-Id: Ifddc446082fb2897f81559517f90e1ee603e13f3
> Signed-off-by: Lukasz Bartosik <lbartosik@marvell.com>
> ---
> examples/ipsec-secgw/event_helper.c | 26 --------------------------
> examples/ipsec-secgw/ipsec-secgw.c | 26 +++++++++++++-------------
> 2 files changed, 13 insertions(+), 39 deletions(-)
>
> diff --git a/examples/ipsec-secgw/event_helper.c b/examples/ipsec-secgw/event_helper.c
> index 076f1f2..da861e4 100644
> --- a/examples/ipsec-secgw/event_helper.c
> +++ b/examples/ipsec-secgw/event_helper.c
> @@ -1526,7 +1526,6 @@ int32_t
> eh_devs_init(struct eh_conf *conf)
> {
> struct eventmode_conf *em_conf;
> - uint16_t port_id;
> int ret;
>
> if (conf == NULL) {
> @@ -1558,16 +1557,6 @@ eh_devs_init(struct eh_conf *conf)
> /* Display the current configuration */
> eh_display_conf(conf);
>
> - /* Stop eth devices before setting up adapter */
> - RTE_ETH_FOREACH_DEV(port_id) {
> -
> - /* Use only the ports enabled */
> - if ((conf->eth_portmask & (1 << port_id)) == 0)
> - continue;
> -
> - rte_eth_dev_stop(port_id);
> - }
> -
> /* Setup eventdev */
> ret = eh_initialize_eventdev(em_conf);
> if (ret < 0) {
> @@ -1589,21 +1578,6 @@ eh_devs_init(struct eh_conf *conf)
> return ret;
> }
>
> - /* Start eth devices after setting up adapter */
> - RTE_ETH_FOREACH_DEV(port_id) {
> -
> - /* Use only the ports enabled */
> - if ((conf->eth_portmask & (1 << port_id)) == 0)
> - continue;
> -
> - ret = rte_eth_dev_start(port_id);
> - if (ret < 0) {
> - EH_LOG_ERR("Failed to start eth dev %d, %d",
> - port_id, ret);
> - return ret;
> - }
> - }
> -
> return 0;
> }
>
> diff --git a/examples/ipsec-secgw/ipsec-secgw.c b/examples/ipsec-secgw/ipsec-secgw.c
> index 5fde4f7..e03bd89 100644
> --- a/examples/ipsec-secgw/ipsec-secgw.c
> +++ b/examples/ipsec-secgw/ipsec-secgw.c
> @@ -2829,6 +2829,19 @@ main(int32_t argc, char **argv)
> if (ret < 0)
> rte_exit(EXIT_FAILURE, "eh_devs_init failed, err=%d\n", ret);
>
> + /* Replicate each context per socket */
> + for (i = 0; i < NB_SOCKETS && i < rte_socket_count(); i++) {
> + socket_id = rte_socket_id_by_idx(i);
> + if ((socket_ctx[socket_id].mbuf_pool != NULL) &&
> + (socket_ctx[socket_id].sa_in == NULL) &&
> + (socket_ctx[socket_id].sa_out == NULL)) {
> + sa_init(&socket_ctx[socket_id], socket_id);
> + sp4_init(&socket_ctx[socket_id], socket_id);
> + sp6_init(&socket_ctx[socket_id], socket_id);
> + rt_init(&socket_ctx[socket_id], socket_id);
> + }
> + }
> +
> /* start ports */
> RTE_ETH_FOREACH_DEV(portid) {
> if ((enabled_port_mask & (1 << portid)) == 0)
> @@ -2866,19 +2879,6 @@ main(int32_t argc, char **argv)
> rte_exit(EXIT_FAILURE, "failed at reassemble init");
> }
>
> - /* Replicate each context per socket */
> - for (i = 0; i < NB_SOCKETS && i < rte_socket_count(); i++) {
> - socket_id = rte_socket_id_by_idx(i);
> - if ((socket_ctx[socket_id].mbuf_pool != NULL) &&
> - (socket_ctx[socket_id].sa_in == NULL) &&
> - (socket_ctx[socket_id].sa_out == NULL)) {
> - sa_init(&socket_ctx[socket_id], socket_id);
> - sp4_init(&socket_ctx[socket_id], socket_id);
> - sp6_init(&socket_ctx[socket_id], socket_id);
> - rt_init(&socket_ctx[socket_id], socket_id);
> - }
> - }
> -
> check_all_ports_link_status(enabled_port_mask);
>
> /* launch per-lcore init on every lcore */
>
next prev parent reply other threads:[~2020-04-15 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 11:32 Lukasz Bartosik
2020-04-15 16:27 ` Lukas Bartosik [C] [this message]
2020-04-15 23:47 ` Ananyev, Konstantin
2020-04-16 12:28 ` [dpdk-dev] [EXT] " Lukas Bartosik [C]
2020-04-21 13:51 ` Lukas Bartosik [C]
2020-04-21 15:18 ` Ananyev, Konstantin
2020-04-22 16:35 ` Anoob Joseph
2020-04-24 12:35 ` Ananyev, Konstantin
2020-04-29 12:52 ` Lukas Bartosik [C]
2020-06-30 19:19 ` Akhil Goyal
2020-07-02 11:47 ` Ananyev, Konstantin
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=139b63ab-6ce0-1657-2754-37e1347143bc@marvell.com \
--to=lbartosik@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=pathreya@marvell.com \
--cc=radu.nicolau@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).