From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f193.google.com (mail-pf0-f193.google.com [209.85.192.193]) by dpdk.org (Postfix) with ESMTP id D7EB42951 for ; Tue, 28 Jun 2016 11:44:38 +0200 (CEST) Received: by mail-pf0-f193.google.com with SMTP id 66so1322634pfy.1 for ; Tue, 28 Jun 2016 02:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=7UIPJtA3fmuzyvzRQm67aOYJe9NaWsFREeqokTiXSv8=; b=St0aZ0xjHT6SHZFfvFqKRzJTG5w7yLMOUBCAEscY/WcOIu+jeNt2iCEht7WyAcR7/P 3FXnUjgy7QORIcHIfltyTT8oTLwPxjGKclPYONGxoL7TER8oCs9XjmvfJk5CY+NKqokl iqR8vfLRdrm0p4aJDIHQ3ORjO9iGceBwsAs3MLNjXLnVlmPxuLbMHE7/0xceoP87L86S /GY8KTHxVN/Z9iIvqcr/0v20K9lrlb24YumwPzYTlo4JPwq1h9enadCFcOeqd18fOmom 1xbUnfFLExoh25QNfip0QFxyKZ8w8G84RVZcG5+zzoPe1NB+YclMrxyBu0cER04ePB5K tJZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=7UIPJtA3fmuzyvzRQm67aOYJe9NaWsFREeqokTiXSv8=; b=D7ymkBpWI+cwlkAhrfP6claQNK1UHzNk9bOgjuGMtm+z7Zc4+fib16A90+iL7K4k6m C8WrL7C0b1BdqVZS9HOPNDkeyJweXlxtZUd8fRLxCS5VAFxPoNTnLT4NCQ/eb2qx5LBK oj+0zHiwzy5krQB+wOrigXwckmdMez2LOfeTlU/6zOamqckgKzAwoRTlx1r9bUf6l31G uALPn0XmgGUUVRTD5P+UZqzyIrdhTSvErUEFnwRlf4GDQn/oLYp8/sRrFQaCAe0Lg0R1 Pe8TqHJe0SVs6tEokWr1qR6TXjf7orlHS5YKXI7ANsx8EWeC8wkLZoqukqsjctBHgKMB ONgA== X-Gm-Message-State: ALyK8tK/+TyWZGxDVknlqp+RFfgRePruEtPmoQQXX7I/XmYSSwErGa5G1mA7E+4PdSXTSw== X-Received: by 10.98.100.14 with SMTP id y14mr265260pfb.84.1467107078246; Tue, 28 Jun 2016 02:44:38 -0700 (PDT) Received: from localhost ([114.143.135.2]) by smtp.gmail.com with ESMTPSA id ct7sm5912154pac.13.2016.06.28.02.44.37 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 28 Jun 2016 02:44:37 -0700 (PDT) References: <87h9cdoo8r.fsf@fatcat.parallelwireless> <87furxon3k.fsf@fatcat.parallelwireless> User-agent: mu4e 0.9.16; emacs 24.5.1 From: Anupam Kapoor To: amartya.das@wipro.com Cc: anupam.kapoor@gmail.com, users@dpdk.org In-reply-to: Date: Tue, 28 Jun 2016 15:14:35 +0530 Message-ID: <87eg7hodfg.fsf@fatcat.parallelwireless> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [dpdk-users] [dpdk-dev] [Crypto-API query] X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 09:44:39 -0000 >>>>> [2016-06-28T12:31:02+0530]: "amartya.das" (amartya.das): moved the discussion to dpdk-users (from dpdk-dev) ,----[ amartya.das ] | But getting same error: | | Not sure about the problem, any path setting wrong so that it is not fetching? `---- couple of things: - assuming standard build paths, can you please check if 'CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y' in your, build/.config ? - if it is, then see if you have bunch of object files in build/build/drivers/crypto/aesni_mb for example, for me i see a bunch of files: -rw-rw-r-- 1 anupam anupam 26068 Jun 28 14:28 librte_pmd_aesni_mb.a -rw-rw-r-- 1 anupam anupam 0 Jun 28 14:28 _postbuild -rw-rw-r-- 1 anupam anupam 0 Jun 28 14:28 _postinstall -rw-rw-r-- 1 anupam anupam 15192 Jun 28 14:28 rte_aesni_mb_pmd.o -rw-rw-r-- 1 anupam anupam 10456 Jun 28 14:28 rte_aesni_mb_pmd_ops.o - if you see this as well, then, while building the l2fwd-crypto application, make sure that you have 'AESNI_MULTI_BUFFER_LIB_PATH' pointing to the correct place. - if this is also true, then check and see if your application contains aes.*pmd symbols e.g. objdump -t build/l2fwd-crypto | grep 'aes.*pmd' - if this gives you something useful, then you are almost there :) running the application e.g. like so: [root@perf3 dpdk-sources]# examples/l2fwd-crypto/build/app/l2fwd-crypto -c 0xc -n 3 --vdev="cryptodev_aesni_mb_pmd,socket_id=0,max_nb_sessions=128" starts doing something sane... couple of minor things: - after building the crypto-multi-buffer support make sure to run the tests as well in 'LibTestApp' if you are running on vcpu's this would most likely fail (no avx support) - please note thtat 'socket_id' in the dpdk-cryptodev page is set to '1' -- thanks anupam