numam-dpdk/examples/packet_ordering/Makefile

# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2010-2014 Intel Corporation

ifeq ($(RTE_SDK),)
$(error "Please define RTE_SDK environment variable")
endif

# Default target, can be overridden by command line or environment
RTE_TARGET ?= x86_64-native-linuxapp-gcc

include $(RTE_SDK)/mk/rte.vars.mk

# binary name
APP = packet_ordering

# all source are stored in SRCS-y
SRCS-y := main.c

CFLAGS += -O3
CFLAGS += $(WERROR_FLAGS)

include $(RTE_SDK)/mk/rte.extapp.mk
examples: use SPDX tag for Intel copyright files Replace the BSD license header with the SPDX tag for files with only an Intel copyright on them. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> 2017-12-19 15:49:02 +00:00			`# SPDX-License-Identifier: BSD-3-Clause`
			`# Copyright(c) 2010-2014 Intel Corporation`
examples/packet_ordering: new sample app This new app makes use of the librte_reorder library. It requires at least 3 lcores for RX, Workers (1 or more) and TX threads. Communication between RX-Workers and Workers-TX is done by using rings. The flow of mbufs is the following: * RX thread gets mbufs from driver, set sequence number and enqueue them in ring. * Workers dequeue mbufs from ring, do some 'work' and enqueue mbufs in ring. * TX dequeue mbufs from ring, inserts them in reorder buffer, drains mbufs from reorder and sends them to the driver. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Declan Doherty <declan.doherty@intel.com> [Thomas: add in examples/Makefile] 2015-02-18 14:58:15 +00:00
			`ifeq ($(RTE_SDK),)`
			`$(error "Please define RTE_SDK environment variable")`
			`endif`

			`# Default target, can be overridden by command line or environment`
ivshmem: remove library and its EAL integration Following discussions on the mailing list [1] and since nobody stood up to implement the necessary cleanups, here is the ivshmem integration removal. There is not much to say about this patch, a lot of code is being removed. The default configuration file for packet_ordering example is replaced with the "native" x86 file. The only tricky part is in eal_memory with the memseg index stuff. More cleanups can be done after this but will come in subsequent patchsets. [1]: http://dpdk.org/ml/archives/dev/2016-June/040844.html Signed-off-by: David Marchand <david.marchand@6wind.com> Acked-by: Panu Matilainen <pmatilai@redhat.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com> 2016-07-29 12:28:36 +00:00			`RTE_TARGET ?= x86_64-native-linuxapp-gcc`
examples/packet_ordering: new sample app This new app makes use of the librte_reorder library. It requires at least 3 lcores for RX, Workers (1 or more) and TX threads. Communication between RX-Workers and Workers-TX is done by using rings. The flow of mbufs is the following: * RX thread gets mbufs from driver, set sequence number and enqueue them in ring. * Workers dequeue mbufs from ring, do some 'work' and enqueue mbufs in ring. * TX dequeue mbufs from ring, inserts them in reorder buffer, drains mbufs from reorder and sends them to the driver. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Declan Doherty <declan.doherty@intel.com> [Thomas: add in examples/Makefile] 2015-02-18 14:58:15 +00:00
			`include $(RTE_SDK)/mk/rte.vars.mk`

			`# binary name`
			`APP = packet_ordering`

			`# all source are stored in SRCS-y`
			`SRCS-y := main.c`

			`CFLAGS += -O3`
			`CFLAGS += $(WERROR_FLAGS)`

			`include $(RTE_SDK)/mk/rte.extapp.mk`