DPDK usage discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: satyavalli rama <satyavalli.rama@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Ipsec-secgw packet processing
Date: Tue, 18 Aug 2020 10:59:53 +0000	[thread overview]
Message-ID: <MN2PR18MB28771AE121FECD62CD699A50DF5C0@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAECt3bNy1CVRtWVunirj3V6pAR0RWQps=kB--+2Vyu6DgnRK5g@mail.gmail.com>

Hi Satya,

Are you attempting to enable inline protocol (IPsec) functionality? If yes, which PMD (& h/w) are you using for the same?

Thanks,
Anoob

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of satyavalli rama
> Sent: Tuesday, August 18, 2020 4:08 PM
> To: dev@dpdk.org; users@dpdk.org
> Subject: Re: [dpdk-dev] Ipsec-secgw packet processing
> 
> We further debugged and we observed that while running ipsec-secgw
> application in transport-mode dpdk-19.02/11, we found that inline packet
> processing is not happening.
> We observed that ol_flags is not setting from driver level. We are expecting
> that , because of ol_flags not set , inline packet processing is not
> happening.Any idea What could be the reason for this, I think ol_flags will be
> configured from driver level Or else do we need to provide any external
> configuration for setting ol_flags.
> And also we are not observing encrypt/decrypt packets on pdump before
> sending packets out from tx-port(rte_eth_tx_burst()).
> Please help us on this...to proceed further.
> 
> Thanks & Regards
> Satya
> 
> 
> 
> On Mon, 17 Aug, 2020, 4:11 pm satyavalli rama, <satyavalli.rama@gmail.com>
> wrote:
> 
> >
> > Hello,
> >
> > While we are running ipsec-secgw application in transport-mode on
> > dpdk-19.02, we found that inline packet processing is not happening.
> >
> > And also we are not observing any encrypt/decrypt packets on pdump
> > before sending packets out from tx-port(rte_eth_tx_burst()).
> >
> > Please help us on how to proceed further.
> >
> > Thanks,
> > Jagadeesh
> >
> >

  reply	other threads:[~2020-08-18 11:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04  7:24 [dpdk-users] l2fwd application are not sending continuous packets Rohit kamble
     [not found] ` <CAMJ3rejbOZ5mzOYyNPFqVk-Scs7CTaVZLUQOd-GMnVpaYf+pmg@mail.gmail.com>
2020-01-06  5:55   ` [dpdk-users] Fwd: " satyavalli rama
2020-01-06  7:07     ` [dpdk-users] " satyavalli rama
2020-01-09  1:55     ` satyavalli rama
2020-01-09  6:12       ` [dpdk-users] [dpdk-dev] " Stephen Hemminger
2020-01-09 10:34         ` satyavalli rama
2020-08-17 10:41     ` [dpdk-users] Ipsec-secgw packet processing satyavalli rama
2020-08-18 10:37       ` satyavalli rama
2020-08-18 10:59         ` Anoob Joseph [this message]
2020-08-19 11:08           ` [dpdk-users] [dpdk-dev] " satyavalli rama
2020-08-26 11:23             ` satyavalli rama
2020-08-31  5:17               ` [dpdk-users] [EXT] " Anoob Joseph
2020-08-31 12:47                 ` Pathak, Pravin
2020-09-01 11:07                   ` [dpdk-users] [dpdk-dev] [EXT] " Iremonger, Bernard

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=MN2PR18MB28771AE121FECD62CD699A50DF5C0@MN2PR18MB2877.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=satyavalli.rama@gmail.com \
    --cc=users@dpdk.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).