From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Pathak, Pravin" <pravin.pathak@intel.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] QAT PMD in multi-process mode
Date: Thu, 24 Oct 2019 17:02:53 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435A217E710@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <168A68C163D584429EF02A476D52744268BDF6B3@FMSMSX108.amr.corp.intel.com>
Hi Pravin,
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Pathak, Pravin
> Sent: Thursday, October 24, 2019 5:12 PM
> To: users@dpdk.org
> Subject: [dpdk-users] QAT PMD in multi-process mode
>
> Hi -
> In multi-process model, if same QAT VF is shared between two processes which are spawned from
> separate executables, primary process give segfault while accessing QAT functions.
> It looks like PMD installs access functions in shared area so when secondary process changes those
> function pointers, they are no longer valid in primary process.
>
http://doc.dpdk.org/guides/cryptodevs/qat.html
states
"Each VF can only be used by one DPDK process. It is not possible to share the same VF across multiple processes, even if these processes are using different acceleration services."
However, we are currently investigating use of a QAT VF in a primary and secondary process - but with some constraints about what can be done in each process, e.g. session init in one process and enqueue/dequeue in the other.
> Is QAT PMD going to modified to support this mode in future?
> Regards
> Pravin
>
>
next prev parent reply other threads:[~2019-10-24 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 16:12 Pathak, Pravin
2019-10-24 17:02 ` Trahe, Fiona [this message]
2019-10-24 17:28 ` Pathak, Pravin
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=348A99DA5F5B7549AA880327E580B435A217E710@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=pravin.pathak@intel.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).