From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Shally.Verma@cavium.com" <Shally.Verma@cavium.com>,
"ahmed.mansour@nxp.com" <ahmed.mansour@nxp.com>,
"ashish.gupta@caviumnetworks.com"
<ashish.gupta@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] lib/compress: clarify when it's ok to clear private_xform data
Date: Tue, 22 May 2018 12:44:31 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CD10ED7@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CD10D55@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch, Pablo
> Sent: Tuesday, May 22, 2018 12:08 PM
> To: Trahe, Fiona <fiona.trahe@intel.com>; dev@dpdk.org
> Cc: Shally.Verma@cavium.com; ahmed.mansour@nxp.com;
> ashish.gupta@caviumnetworks.com
> Subject: Re: [dpdk-dev] [PATCH] lib/compress: clarify when it's ok to clear
> private_xform data
>
>
>
> > -----Original Message-----
> > From: Trahe, Fiona
> > Sent: Tuesday, May 22, 2018 11:34 AM
> > To: dev@dpdk.org
> > Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Trahe,
> > Fiona <fiona.trahe@intel.com>; Shally.Verma@cavium.com;
> > ahmed.mansour@nxp.com; ashish.gupta@caviumnetworks.com
> > Subject: [PATCH] lib/compress: clarify when it's ok to clear
> > private_xform data
> >
> > As the private_xform data can be shared by many operations and across
> > queue_pairs, it would be performance impacting for PMDs to track
> > inflights associated with one. It makes more sense to push the
> > responsibility to the application to keep track of its usage and only
> > delete the private_xform when there are no more ops using it.
> >
> > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2018-05-22 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:33 Fiona Trahe
2018-05-22 11:07 ` De Lara Guarch, Pablo
2018-05-22 12:44 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8976CD10ED7@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=Shally.Verma@cavium.com \
--cc=ahmed.mansour@nxp.com \
--cc=ashish.gupta@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).