DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Declan Doherty <declan.doherty@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	deepak.k.jain@intel.com
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] cryptodev - Session and queue pair relationship
Date: Tue, 14 Feb 2017 11:43:42 +0000	[thread overview]
Message-ID: <640d1f93-fb38-711d-2b0e-33c2c6d63ba1@intel.com> (raw)
In-Reply-To: <ae911a68-af2f-320c-e351-f327031e26f2@nxp.com>

Hi Akhil,

>>
> Thanks for your feedback Declan,
> The suggestion from Fiona looks good. Should I send the patch for this 
> or is it already in discussion in some different thread?
>
> Also, if this new API is added, there would be corresponding change in 
> the ipsec-secgw application as well.

I am looking forward to see those changes in ipsec-secgw.
Mostly I am interesting in seeing how you plan to allocate resources 
(queue_pairs) when having multiple cores/workers.

Regards,
Sergio

> This API should be optional and underlying implementation may or may 
> not implement this API.
>
> Regards,
> Akhil
>
>

      parent reply	other threads:[~2017-02-14 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 13:35 Akhil Goyal
2017-02-07 20:52 ` Declan Doherty
2017-02-13 14:38   ` Akhil Goyal
2017-02-13 14:44     ` Trahe, Fiona
2017-02-13 15:09       ` Trahe, Fiona
2017-02-14 11:43     ` Sergio Gonzalez Monroy [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=640d1f93-fb38-711d-2b0e-33c2c6d63ba1@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=pablo.de.lara.guarch@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).