From: "Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
To: Shijith Thotton <sthotton@marvell.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v5] app/eventdev: add crypto producer mode
Date: Wed, 16 Feb 2022 07:49:03 +0000 [thread overview]
Message-ID: <PH0PR11MB48240C32E964F130340359A1E8359@PH0PR11MB4824.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR18MB442948AEABBF9579232BC6DCD9359@SJ0PR18MB4429.namprd18.prod.outlook.com>
Hi Shijith,
> -----Original Message-----
> From: Shijith Thotton <sthotton@marvell.com>
> Sent: Wednesday, February 16, 2022 12:39 PM
> To: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>
> Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; dev@dpdk.org
> Subject: RE: [PATCH v5] app/eventdev: add crypto producer mode
>
> >>
> >> In crypto producer mode, producer core enqueues cryptodev with
> >> software generated crypto ops and worker core dequeues crypto
> >> completion events from the eventdev. Event crypto metadata used for
> >> above processing is pre- populated in each crypto session.
> >>
> >> Parameter --prod_type_cryptodev can be used to enable crypto producer
> >> mode. Parameter --crypto_adptr_mode can be set to select the crypto
> >> adapter mode, 0 for OP_NEW and 1 for OP_FORWARD.
> >>
> >> This mode can be used to measure the performance of crypto adapter.
> >>
> >> Example:
> >> ./dpdk-test-eventdev -l 0-2 -w <EVENTDEV> -w <CRYPTODEV> -- \
> >> --prod_type_cryptodev --crypto_adptr_mode 1 --test=perf_atq \
> >> --stlist=a --wlcores 1 --plcores 2
> >>
> >I still see error with both OP_NEW and OP_FORWARD mode. Can't run the
> test.
> >root@xdp-dev:/home/intel/abhi/dpdk-next-eventdev/abhi# ./app/dpdk-
> test-
> >eventdev -l 0-8 -s 0xf0 --vdev=event_sw0 --vdev="crypto_null" -- --
> >prod_type_cryptodev --crypto_adptr_mode 1 --test=perf_queue --stlist=a
> >-- wlcores 1 --plcores 2
> >EAL: Detected CPU lcores: 96
> >EAL: Detected NUMA nodes: 2
> >EAL: Detected static linkage of DPDK
> >EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> >EAL: Selected IOVA mode 'PA'
> >EAL: VFIO support initialized
> >CRYPTODEV: Creating cryptodev crypto_null
> >
> >CRYPTODEV: Initialisation parameters - name: crypto_null,socket id: 0,
> >max queue
> >pairs: 8
> >TELEMETRY: No legacy callbacks, legacy socket not created
> > driver : event_sw
> > test : perf_queue
> > dev : 0
> > verbose_level : 1
> > socket_id : -1
> > pool_sz : 16384
> > main lcore : 0
> > nb_pkts : 67108864
> > nb_timers : 100000000
> > available lcores : {0 1 2 3 8}
> > nb_flows : 1024
> > worker deq depth : 16
> > fwd_latency : false
> > nb_prod_lcores : 1
> > producer lcores : {2}
> > nb_worker_lcores : 1
> > worker lcores : {1}
> > nb_stages : 1
> > nb_evdev_ports : 2
> > nb_evdev_queues : 1
> > queue_priority : false
> > sched_type_list : {A}
> > crypto adapter mode : OP_FORWARD
> > nb_cryptodev : 1
> > prod_type : Event crypto adapter producers
> > prod_enq_burst_sz : 1
> >CRYPTODEV: elt_size 0 is expanded to 208
> >
> >error: perf_event_crypto_adapter_setup() crypto adapter OP_FORWARD
> mode
> >unsupported
> >
> >error: main() perf_queue: eventdev setup failed
> >
>
> No change from previous version.
> Apply the patch "[RFC] app/eventdev: add software crypto adapter support"
> for using SW.
I see. Please send out next patchset once you have fix.
Thanks,
Abhinandan
next prev parent reply other threads:[~2022-02-16 7:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 19:53 [PATCH] " Shijith Thotton
2021-12-21 8:51 ` [PATCH v2] " Shijith Thotton
2021-12-30 11:56 ` Gujjar, Abhinandan S
2022-01-03 6:04 ` Shijith Thotton
2022-01-03 8:46 ` Gujjar, Abhinandan S
2022-01-03 9:14 ` Shijith Thotton
2022-01-04 15:28 ` Aaron Conole
2022-01-04 15:49 ` [EXT] " Shijith Thotton
2022-01-04 10:30 ` [PATCH v3] " Shijith Thotton
2022-01-21 12:25 ` Jerin Jacob
2022-01-23 16:56 ` Gujjar, Abhinandan S
2022-01-23 18:44 ` Gujjar, Abhinandan S
2022-01-24 6:09 ` Shijith Thotton
2022-01-24 6:59 ` Shijith Thotton
2022-01-25 14:15 ` Gujjar, Abhinandan S
2022-01-25 13:39 ` Gujjar, Abhinandan S
2022-02-08 17:00 ` Shijith Thotton
2022-02-14 15:26 ` Jerin Jacob
2022-02-14 15:31 ` Gujjar, Abhinandan S
2022-02-08 16:33 ` [PATCH v4] " Shijith Thotton
2022-02-15 6:03 ` Gujjar, Abhinandan S
2022-02-15 16:08 ` Shijith Thotton
2022-02-15 16:46 ` Gujjar, Abhinandan S
2022-02-15 16:56 ` [PATCH v5] " Shijith Thotton
2022-02-16 4:47 ` Gujjar, Abhinandan S
2022-02-16 7:08 ` Shijith Thotton
2022-02-16 7:49 ` Gujjar, Abhinandan S [this message]
2022-02-16 8:44 ` Jerin Jacob
2022-02-16 8:54 ` Jerin Jacob
2022-02-17 5:33 ` Gujjar, Abhinandan S
2022-02-21 13:10 ` Van Haaren, Harry
2022-02-22 7:03 ` Shijith Thotton
2022-02-23 9:02 ` Gujjar, Abhinandan S
2022-02-23 10:02 ` Shijith Thotton
2022-02-23 10:13 ` Van Haaren, Harry
2022-02-23 16:33 ` Gujjar, Abhinandan S
2022-02-23 17:02 ` Shijith Thotton
2022-02-17 6:56 ` [EXT] " Akhil Goyal
2022-02-18 12:00 ` Shijith Thotton
2022-02-18 12:11 ` [PATCH v6] " Shijith Thotton
2022-02-24 4:46 ` [PATCH v7] " Shijith Thotton
2022-02-24 6:18 ` Gujjar, Abhinandan S
2022-02-24 7:58 ` Jerin Jacob
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=PH0PR11MB48240C32E964F130340359A1E8359@PH0PR11MB4824.namprd11.prod.outlook.com \
--to=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=sthotton@marvell.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).