c: jer...@marvell.com; akhil.go...@nxp.com; Vangati, Narender
> ; nd ; Honnappa Nagarahalli
> ; nd
> Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback functions
>
>
>
> > > > > > Hi Abhinandan,
> > > > > >
> > > &g
0
> >0 0.8245
> 0.4221 2656.14
> >7 64 3210001000 0
> >0 0.8261
> 0.4229 2651.15
>
> So, if I can read numbers properly for not-armed callback impact is
&
jer...@marvell.com; akhil.go...@nxp.com; Vangati, Narender
> > ; nd ; nd
> > Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback
> > functions
> >
> >
> >
> > Hi Abhinandan,
> >
> > >
> > > Hi Konstantin,
> > >
; nd ; nd
> Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback functions
>
>
>
> Hi Abhinandan,
>
> >
> > Hi Konstantin,
> >
> >
> > > -Original Message-
> > > From: Ananyev, Konstantin
> > > Sent: Frid
; Cc: jer...@marvell.com; akhil.go...@nxp.com; Vangati, Narender
> > ; nd ; nd
> > Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback
> > functions
> >
> > Hi Abhinandan,
> >
> > >
> > > Hi Konstantin & Honnappa,
> >
; nd ; nd
> Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback functions
>
> Hi Abhinandan,
>
> >
> > Hi Konstantin & Honnappa,
> >
> > Thanks for all the inputs and feedback.
> >
> > @Ananyev, Konstantin,
> > I have measured
in
> > Sent: Tuesday, September 29, 2020 2:33 PM
> > To: Honnappa Nagarahalli ; Gujjar,
> > Abhinandan S ; dev@dpdk.org; Doherty, Declan
> >
> > Cc: jer...@marvell.com; akhil.go...@nxp.com; Vangati, Narender
> > ; nd ; nd
> > Subj
gt; -Original Message-
> From: Ananyev, Konstantin
> Sent: Tuesday, September 29, 2020 2:33 PM
> To: Honnappa Nagarahalli ; Gujjar,
> Abhinandan S ; dev@dpdk.org; Doherty, Declan
>
> Cc: jer...@marvell.com; akhil.go...@nxp.com; Vangati, Narender
> ; nd ; nd
> S
>
> > >
> > > > > > > > > > >
> > > > > > > > > > > +#ifdef RTE_CRYPTODEV_CALLBACKS int
> > > > > > > > > > > +rte_cryptodev_rcu_qsbr_add(uint8_t dev_id, struct
> > > > > > > > > > > +rte_rcu_qsbr
> > > > > > > > > > > +*qsbr) {
> > > > > > > > > > > +
> > > > > > > > > > > + struct rte_cryptode
> >
> > > > > > > > > >
> > > > > > > > > > +#ifdef RTE_CRYPTODEV_CALLBACKS int
> > > > > > > > > > +rte_cryptodev_rcu_qsbr_add(uint8_t dev_id, struct
> > > > > > > > > > +rte_rcu_qsbr
> > > > > > > > > > +*qsbr) {
> > > > > > > > > > +
> > > > > > > > > > + struct rte_cryptodev *dev;
> > > > >
>
> > > > > > > > >
> > > > > > > > > +#ifdef RTE_CRYPTODEV_CALLBACKS int
> > > > > > > > > +rte_cryptodev_rcu_qsbr_add(uint8_t dev_id, struct
> > > > > > > > > +rte_rcu_qsbr
> > > > > > > > > +*qsbr) {
> > > > > > > > > +
> > > > > > > > > + struct rte_cryptodev *dev;
> > > > > > > > > +
>
>
> In an eventdev world, multiple workers (with ordered queue) will be working
> on IPsec ESP processing. The ESP header's sequence number is unique and
> has to be sequentially incremented in an orderly manner.
> This rises a need for incrementing sequence number in crypto stage
> especially i
> > > > > > > >
> > > > > > > > +#ifdef RTE_CRYPTODEV_CALLBACKS int
> > > > > > > > +rte_cryptodev_rcu_qsbr_add(uint8_t dev_id, struct
> > > > > > > > +rte_rcu_qsbr
> > > > > > > > +*qsbr) {
> > > > > > > > +
> > > > > > > > + struct rte_cryptodev *dev;
> > > > > > > > +
> > > > > > > > +
> > > > > > >
> > > > > > > In an eventdev world, multiple workers (with ordered queue)
> > > > > > > will be working on IPsec ESP processing. The ESP header's
> > > > > > > sequence number is unique and has to be sequentially
> > > > > > > incremented in an orderly
> > > > manner.
> > > > > > >
>
> > > > > >
> > > > > > In an eventdev world, multiple workers (with ordered queue)
> > > > > > will be working on IPsec ESP processing. The ESP header's
> > > > > > sequence number is unique and has to be sequentially
> > > > > > incremented in an orderly
> > > manner.
> > > > > > This rises
> > > > >
> > > > > In an eventdev world, multiple workers (with ordered queue) will
> > > > > be working on IPsec ESP processing. The ESP header's sequence
> > > > > number is unique and has to be sequentially incremented in an orderly
> > manner.
> > > > > This rises a need for incrementing seque
rg
> Cc: Doherty, Declan ; jer...@marvell.com;
> akhil.go...@nxp.com; Vangati, Narender
> Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback
> functions
>
>
>
> > > >
> > > > In an eventdev world, multiple workers (with ordered qu
> > >
> > > In an eventdev world, multiple workers (with ordered queue) will be
> > > working on IPsec ESP processing. The ESP header's sequence number is
> > > unique and has to be sequentially incremented in an orderly manner.
> > > This rises a need for incrementing sequence number in crypto
arender ;
> Gujjar, Abhinandan S
> Subject: RE: [dpdk-dev] [v2 1/2] cryptodev: support enqueue callback
> functions
>
> Hi Guijjar,
>
> >
> > In an eventdev world, multiple workers (with ordered queue) will be
> > working on IPsec ESP processing. The ESP header'
Hi Guijjar,
>
> In an eventdev world, multiple workers (with ordered queue) will be
> working on IPsec ESP processing. The ESP header's sequence number is
> unique and has to be sequentially incremented in an orderly manner.
> This rises a need for incrementing sequence number in crypto stage
> e
> -Original Message-
> From: Honnappa Nagarahalli
> Sent: Thursday, September 10, 2020 4:19 AM
> To: Gujjar, Abhinandan S ; dev@dpdk.org
> Cc: Doherty, Declan ; jer...@marvell.com;
> akhil.go...@nxp.com; Vangati, Narender ;
> Ananyev, Konstantin ; nd ;
> Honnappa Nagarahalli ; nd
>
> S
> >
> > In an eventdev world, multiple workers (with ordered queue) will be
> > working on IPsec ESP processing. The ESP header's sequence number is
> > unique and has to be sequentially incremented in an orderly manner.
> > This rises a need for incrementing sequence number in crypto stage
> > e
+Konstantin & Honnappa
> -Original Message-
> From: Gujjar, Abhinandan S
> Sent: Tuesday, September 8, 2020 12:40 PM
> To: dev@dpdk.org
> Cc: Doherty, Declan ; jer...@marvell.com;
> akhil.go...@nxp.com; Vangati, Narender ;
> Gujjar, Abhinandan S
> Subject: [v2 1/2] cryptodev: support enq
In an eventdev world, multiple workers (with ordered queue) will be
working on IPsec ESP processing. The ESP header's sequence number is
unique and has to be sequentially incremented in an orderly manner.
This rises a need for incrementing sequence number in crypto stage
especially in event crypto
24 matches
Mail list logo
