DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Akhil Goyal <akhil.goyal@nxp.com>
Cc: dpdk-dev <dev@dpdk.org>, Hemant Agrawal <hemant.agrawal@nxp.com>,
	anoobj@marvell.com, Jerin Jacob <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/dpaa_sec: support event crypto adapter
Date: Mon, 30 Sep 2019 20:23:53 +0530	[thread overview]
Message-ID: <CALBAE1PDtcSiPf7zd4vYJn-Y6ERWNUZKXgJ7=qcawOE7-tmdPA@mail.gmail.com> (raw)
In-Reply-To: <20190906131256.23367-1-akhil.goyal@nxp.com>

On Fri, Sep 6, 2019 at 6:57 PM Akhil Goyal <akhil.goyal@nxp.com> wrote:
>
> dpaa_sec hw queues can be attached to a hw dpaa event
> device and the application can configure the event
> crypto adapter to access the dpaa_sec packets using
> hardware events.
> This patch defines APIs which can be used by the
> dpaa event device to attach/detach dpaa_sec queues.
>
> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>

meson cross-build is failing with this patch. Please fix it in v2 and
If it makes sense then add this new feature in release notes.

Commands to reproduce:

meson build --cross=config/arm/arm64_armv8_linux_gcc
ninja -C build

FAILED: drivers/a715181@@tmp_rte_pmd_dpaa_event@sta/event_dpaa_dpaa_eventdev.c.o
aarch64-linux-gnu-gcc -Idrivers/a715181@@tmp_rte_pmd_dpaa_event@sta
-Idrivers -I../drivers -Idrivers/event/dpaa -I../drivers/event/dpaa
-Ilib/librte_eventdev -I../lib/librte_eventdev -I. -I../ -Iconfig
-I../config -Ilib/librte_eal/common/in
clude -I../lib/librte_eal/common/include
-I../lib/librte_eal/linux/eal/include -Ilib/librte_eal/common
-I../lib/librte_eal/common -Ilib/librte_eal/common/include/arch/arm
-I../lib/librte_eal/common/include/arch/arm -Ilib/librte_eal -I../lib
/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs
-Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_ethdev
-I../lib/librte_ethdev -Ilib/librte_net -I../lib/librte_net
-Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../l
ib/librte_mempool -Ilib/librte_meter -I../lib/librte_meter
-Ilib/librte_hash -I../lib/librte_hash -Ilib/librte_timer
-I../lib/librte_timer -Ilib/librte_cryptodev -I../lib/librte_cryptodev
-Idrivers/net/dpaa -I../drivers/net/dpaa -Idrivers/b
us/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux
-Ilib/librte_pci -I../lib/librte_pci -Idrivers/bus/vdev
-I../drivers/bus/vdev -Idrivers/mempool/dpaa -I../drivers/mempool/dpaa
-Idrivers/bus/dpaa -I../drivers/bus/dpaa -I../drivers/bus/
dpaa/include -I../drivers/bus/dpaa/base/qbman -Idrivers/common/dpaax
-I../drivers/common/dpaax -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O3 -include rte_config.h
-Wunused-parameter -Wsign-compare -Wcast-qu
al -Wno-address-of-packed-member -D_GNU_SOURCE -fPIC
-march=armv8-a+crc -Wno-format-truncation -DALLOW_EXPERIMENTAL_API -MD
-MQ 'drivers/a715181@@tmp_rte_pmd_dpaa_event@sta/event_dpaa_dpaa_eventdev.c.o'
-MF 'drivers/a715181@@tmp_rte_pmd_dpa
a_event@sta/event_dpaa_dpaa_eventdev.c.o.d' -o
'drivers/a715181@@tmp_rte_pmd_dpaa_event@sta/event_dpaa_dpaa_eventdev.c.o'
-c ../drivers/event/dpaa/dpaa_eventdev.c
../drivers/event/dpaa/dpaa_eventdev.c:37:10: fatal error:
dpaa_sec_event.h: No such file or directory
   37 | #include <dpaa_sec_event.h>
      |          ^~~~~~~~~~~~~~~~~~

  parent reply	other threads:[~2019-09-30 14:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 13:12 Akhil Goyal
2019-09-06 13:12 ` [dpdk-dev] [PATCH 2/2] event/dpaa: " Akhil Goyal
2019-09-26 17:59   ` Jerin Jacob
2019-09-30 14:53 ` Jerin Jacob [this message]
2019-09-30 20:13   ` [dpdk-dev] [PATCH 1/2] crypto/dpaa_sec: " Akhil Goyal
2019-10-01  3:11     ` Jerin Jacob
2019-10-01  6:31       ` Akhil Goyal
2019-10-01 13:15         ` Jerin Jacob
2019-09-30 19:13 ` [dpdk-dev] [PATCH v2 0/2] dpaa_sec: " Akhil Goyal
2019-09-30 19:13   ` [dpdk-dev] [PATCH v2 1/2] crypto/dpaa_sec: " Akhil Goyal
2019-09-30 19:13   ` [dpdk-dev] [PATCH v2 2/2] event/dpaa: " Akhil Goyal
2019-10-04 11:26   ` [dpdk-dev] [PATCH v3 0/2] dpaa_sec: " Akhil Goyal
2019-10-04 11:26     ` [dpdk-dev] [PATCH v3 1/2] crypto/dpaa_sec: " Akhil Goyal
2019-10-04 11:26     ` [dpdk-dev] [PATCH v3 2/2] event/dpaa: " Akhil Goyal
2019-10-09 12:10     ` [dpdk-dev] [PATCH v3 0/2] dpaa_sec: " Akhil Goyal

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='CALBAE1PDtcSiPf7zd4vYJn-Y6ERWNUZKXgJ7=qcawOE7-tmdPA@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.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).