DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anupam Kapoor <anupam.kapoor@gmail.com>
To: amartya.das@wipro.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Crypto-API query]
Date: Tue, 28 Jun 2016 11:21:00 +0530	[thread overview]
Message-ID: <87h9cdoo8r.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <PS1PR03MB1883F8E1E6AF0137396E2FCDED220@PS1PR03MB1883.apcprd03.prod.outlook.com>


>>>>> [2016-06-28T10:57:02+0530]: "amartya.das" (amartya.das):
,----[ amartya.das ]
| Is it possible to use Crypto API with virtual device without VFIO and by using UIO only.
`----
i have just taken a cursory look at the l2fwd-crypto, and it seems it is
possible to have sw-only crypto devices...

---
thanks
anupam

  reply	other threads:[~2016-06-28  5:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  5:27 amartya.das
2016-06-28  5:51 ` Anupam Kapoor [this message]
2016-06-28  6:09   ` amartya.das
2016-06-28  6:15     ` Anupam Kapoor
2016-06-28  7:01       ` amartya.das

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=87h9cdoo8r.fsf@fatcat.parallelwireless \
    --to=anupam.kapoor@gmail.com \
    --cc=amartya.das@wipro.com \
    --cc=dev@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).