[SPDK] Re: Encryption on SPDK

Luse, Paul E <paul.e.luse at intel.com>
Newsgroups dev.linux.lists.spdk
Message-ID <[email protected]>
Hi Lihui,

Sure, we can help you!  Your steps below are correct and will enable crypto using the software DPDK PMD.  If you want to use QAT you'd use "crypto_qat" in pace of " crypto_aesni_mb" but you'd need to have the QAT driver all installed and setup.  I'd say make sure SW works first and then if you want to go that route we can do that.

So once you've done the steps below you can confirm that the bdev created is named CryNvmeA by running the RPC " bdev_get_bdevs"

If that's working the next step would be to access the block device from your app, I assume you are using vhost, do you know how to configure and run some IO there?  There are some other tools we can use to baseline your system too, we have a tool called bdevperf for example but I won't go into how to do that until I hear more about how you intend to access the bdev

Thx
Paul



On 8/3/20, 6:03 PM, "lihui.zhang(a)intel.com" <lihui.zhang(a)intel.com> wrote:

    Hi,
    We are now setting up a SPDK enviornment, some questions on encryption of block dev, thanks!
    1.	How to enable encryption of block dev?
    2.	How to configure software and hardware(through cryptodev) encryption?
    3.	How to validate?


    We tried below steps to enable encrypted partition, is there any method to validate whether it is works or not? 
    1.	Configure and compile SPDK:
    HUGEMEM=8192 ./scripts/setup.sh
    ./configure --with-vhost  --with-crypto
    make -j32

    2.Encryption:
    ./build/bin/vhost -i 0
    ./scripts/rpc.py construct_nvme_bdev -b Nvme01 -t pcie -a 0000:81:00.0
    ./scripts/rpc.py bdev_crypto_create NVMe0n1 CryNvmeA crypto_aesni_mb 0123456789123456

    Thanks!
    _______________________________________________
    SPDK mailing list -- spdk(a)lists.01.org
    To unsubscribe send an email to spdk-leave(a)lists.01.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.