DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jayakumar, Muthurajan" <muthurajan.jayakumar@intel.com>
To: Prashant Upadhyaya <praupadhyaya@gmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Regarding Hardware Crypto Accelerator
Date: Mon, 29 Sep 2014 17:25:39 +0000	[thread overview]
Message-ID: <5D695A7F6F10504DBD9B9187395A21797D13D0A7@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <CAPBAu3UvNarMJS0w_dL3+diY_8mDTNn6DFhSu7w0qfhGuLQqHg@mail.gmail.com>

Prashant, 

Please find Chapter 19 of the Sample Application User Guide http://dpdk.org/doc/intel/dpdk-sample-apps-1.7.0.pdf useful for reference.
ColetoCreek configuration (refer Ch 19.3.1)

Regards, 


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Prashant Upadhyaya
Sent: Monday, September 29, 2014 10:06 AM
To: dev@dpdk.org
Subject: [dpdk-dev] Regarding Hardware Crypto Accelerator

Hi,

Currently I have a machine with Xeon processor and it does not have a hardware crypto accelerator. I am running my DPDK based application successfully on it.

Now I want to use a hardware crypto accelerator and use it with DPDK for IPSec operations in my application I am planning to buy the following --
PE3iS4CO2 -- Silicom's Quad HW Accelerator Crypto Compression PCI Express Gen 3.0 Server Adapter / ColetoCreek SKU2

Can somebody advise if this would work properly with DPDK or is there any other catch involved which I should be careful about before I go ahead and invest on the equipment, would really appreciate any advice.

Regards
-Prashant

      reply	other threads:[~2014-09-29 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 17:05 Prashant Upadhyaya
2014-09-29 17:25 ` Jayakumar, Muthurajan [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=5D695A7F6F10504DBD9B9187395A21797D13D0A7@ORSMSX112.amr.corp.intel.com \
    --to=muthurajan.jayakumar@intel.com \
    --cc=dev@dpdk.org \
    --cc=praupadhyaya@gmail.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).