DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Volodymyr Fialko <vfialko@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Volodymyr Fialko <vfialko@marvell.com>
Subject: RE: [PATCH] app/test: add event inline security tests
Date: Tue, 21 Jun 2022 18:02:09 +0000	[thread overview]
Message-ID: <CO6PR18MB4484B2F15B7D09449A08C824D8B39@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220530133906.1139270-1-vfialko@marvell.com>

> Enable ability to run inline security tests using event
> API(rte_event_eth_tx_adapter_enqueue/rte_event_dequeue_burst).
> New test command - event_inline_ipsec_autotest will run same list of
> test cases as inline_ipsec_autotest, but packets will go through eventdev.
> 
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
> ---
Please fix compilation with mingw. Mingw does not enable eventdev, hence you need to add a dependency while
Compiling this test so that mingw skip compiling this test.

ninja: Entering directory `./build-x86-mingw'
[1/2] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_security_inline_proto.c.obj'.
FAILED: app/test/3062f5d@@dpdk-test@exe/test_security_inline_proto.c.obj
ccache x86_64-w64-mingw32-gcc -Iapp/test/3062f5d@@dpdk-test@exe -Iapp/test -I../app/test -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/windows/include -I../lib/eal/windows/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/kvargs -I../lib/kvargs -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Ilib/mempool -I../lib/mempool -Ilib/mbuf -I../lib/mbuf -Ilib/net -I../lib/net -Ilib/meter -I../lib/meter -Ilib/ethdev -I../lib/ethdev -Ilib/pci -I../lib/pci -Ilib/cmdline -I../lib/cmdline -Ilib/metrics -I../lib/metrics -Ilib/hash -I../lib/hash -Ilib/timer -I../lib/timer -Ilib/bitratestats -I../lib/bitratestats -Ilib/cfgfile -I../lib/cfgfile -Ilib/cryptodev -I../lib/cryptodev -Ilib/gpudev -I../lib/gpudev -Ilib/gro -I../lib/gro -Ilib/gso -I../lib/gso -Ilib/latencystats -I../lib/latencystats -Ilib/dmadev -I../lib/dmadev -Ilib/security -I../lib/security -Ilib/stack -I../lib/stack -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/windows -Idrivers/bus/vdev -I../drivers/bus/vdev -Idrivers/mempool/ring -I../drivers/mempool/ring -Idrivers/mempool/stack -I../drivers/mempool/stack -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wextra -Werror -O2 -g -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -D_WIN32_WINNT=0x0A00 -D__USE_MINGW_ANSI_STDIO -march=native -DALLOW_EXPERIMENTAL_API -Wno-format-truncation -fno-strict-aliasing -DALLOW_INTERNAL_API -MD -MQ 'app/test/3062f5d@@dpdk-test@exe/test_security_inline_proto.c.obj' -MF 'app/test/3062f5d@@dpdk-test@exe/test_security_inline_proto.c.obj.d' -o 'app/test/3062f5d@@dpdk-test@exe/test_security_inline_proto.c.obj' -c ../app/test/test_security_inline_proto.c
../app/test/test_security_inline_proto.c:10:10: fatal error: rte_eventdev.h: No such file or directory
   10 | #include <rte_eventdev.h>
      |          ^~~~~~~~~~~~~~~~
compilation terminated.

      parent reply	other threads:[~2022-06-21 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 13:39 Volodymyr Fialko
2022-06-21 12:58 ` Akhil Goyal
2022-06-21 18:02 ` Akhil Goyal [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=CO6PR18MB4484B2F15B7D09449A08C824D8B39@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=vfialko@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).