DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Lukas Bartosik [C]" <lbartosik@marvell.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	Anoob Joseph <anoobj@marvell.com>
Cc: "Nicolau, Radu" <radu.nicolau@intel.com>,
	Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"orika@mellanox.com" <orika@mellanox.com>,
	"Doherty, Declan" <declan.doherty@intel.com>,
	"Drost, MariuszX" <mariuszx.drost@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [EXT] RE: [PATCH] examples/ipsec-secgw: fix dropping of initial IPsec pkts
Date: Tue, 30 Jun 2020 19:19:08 +0000	[thread overview]
Message-ID: <VI1PR04MB3168F1E013988B556168810CE66F0@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <741fab27-510d-a66e-25c1-5437985098bf@marvell.com>

Hi Lukasz/Konstantin,

> >
> > I still not sure why is that big deal, but ok, can we then just do
> > it in a different way for poll vs event mode for now:
> > for event mode do dev_start() after sa_init(),
> > for poll mode leave things as it (dev_start(), then sa_init()).
> > Would that address the issue?
> >
> 
> [Lukasz] We would prefer not to split behaviour of poll and event modes
> because of workarounds.
> Currently sa_init() is being done after dev_start() a result of a workaround for
> ixgbe driver.
> IMHO correct order is to create flows, SAs and as a last step do dev_start() when
> all necessary configuration is in place. We can wait for the fix in the ixgbe driver.
> 

Any updates on this patch for 20.08 release cycle?
Is Intel planning for the fix in ixgbe driver?

Regards,
Akhil

  reply	other threads:[~2020-06-30 19:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 11:32 [dpdk-dev] " Lukasz Bartosik
2020-04-15 16:27 ` Lukas Bartosik [C]
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 [this message]
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=VI1PR04MB3168F1E013988B556168810CE66F0@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=lbartosik@marvell.com \
    --cc=mariuszx.drost@intel.com \
    --cc=orika@mellanox.com \
    --cc=pathreya@marvell.com \
    --cc=radu.nicolau@intel.com \
    --cc=wenzhuo.lu@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).