[dpdk-dev] [PATCH v6 0/8] Add virtio support for arm/arm64

Hi, Patch series to allow access to virtio using vfio interface. Tested for vfio-noiommu mode for x86_64/arm64{thunderX} platform. patch series builds successfully for armv7/v8/x86_64/i686. Patchset rebased on yuan's under review virtio-1.0 v2 patchset. Refer my public branch [1] Step to enable

[dpdk-dev] [PATCH v6 8/8] virtio: do not parse if interface is vfio

If virtio interface attached to vfio driver then do not parse for virtio resource. Instead exit with return 0; Signed-off-by: Santosh Shukla --- v5-->v6: - Removed _noimmu and using deafult rte_kdrv_vfio for drv check. drivers/net/virtio/virtio_pci.c |4 +++- 1 file changed, 3

[dpdk-dev] [PATCH v6 7/8] virtio: extend pci rw api for vfio

So far virtio handle rw access for uio / ioport interface, This patch to extend the support for vfio. Signed-off-by: Santosh Shukla --- drivers/net/virtio/virtio_io.h |2 +- drivers/net/virtio/virtio_pci.c | 110 ++- 2 files changed, 98 insertions(+),

[dpdk-dev] [PATCH v6 6/8] virtio: add vfio api to rd/wr ioport space

For vfio case - Use pread/pwrite api to access virtio ioport space. Signed-off-by: Santosh Shukla Signed-off-by: Rizwan Ansari Signed-off-by: Rakesh Krishnamurthy --- v5-->v6: - renamed inport_in/out to vfio_in/out - Renamed file from virtio_vfio_rw.h to virtio_vfio_io.h

[dpdk-dev] [PATCH v6 5/8] virtio: move io header and api from virtio_pci.h

Moving io api and header file i.e. sys/io.h to separate file virtio_io.h Signed-off-by: Santosh Shukla --- v5-->v6: - included new file virtio_io.h, has in/out api and sys/io.h. drivers/net/virtio/virtio_io.h | 114 +++ drivers/net/virtio/virtio_pci.c |

[dpdk-dev] [PATCH v6 4/8] virtio: Introduce config RTE_VIRTIO_INC_VECTOR

- virtio_recv_pkts_vec and other virtio vector friend apis are written for sse/avx instructions. For arm64 in particular, virtio vector implementation does not exist(todo). So virtio pmd driver wont build for targets like i686, arm64. By making RTE_VIRTIO_INC_VECTOR=n, Driver can build for

[dpdk-dev] [PATCH v6 3/8] eal/linux: never check iopl for arm

iopl() syscall not supported in linux-arm/arm64 so always return 0 value. Signed-off-by: Santosh Shukla Suggested-by: Stephen Hemminger Acked-by: Jan Viktorin Acked-by: David Marchand --- lib/librte_eal/linuxapp/eal/eal.c |2 ++ 1 file changed, 2 insertions(+) diff --git

[dpdk-dev] [PATCH v6 2/8] linuxapp/vfio: ignore mapping for ioport region

vfio_pci_mmap() try to map all pci bars. ioport region are not mapped in vfio/kernel so ignore mmaping for ioport. Signed-off-by: Santosh Shukla --- lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 20 1 file changed, 20 insertions(+) diff --git

[dpdk-dev] [PATCH v6 1/8] eal: pci: add api to rd/wr pci bar region

Introducing below api for pci bar region rd/wr. Api's are: - rte_eal_pci_read_bar - rte_eal_pci_write_bar Signed-off-by: Santosh Shukla --- v5-->v6: - update api infor in rte_eal_version.map file suggested by david manchand. lib/librte_eal/bsdapp/eal/eal_pci.c | 19

[dpdk-dev] [PATCH 0/5] add external mempool manager

On Fri, Jan 29, 2016 at 01:40:40PM +, Hunt, David wrote: > On 28/01/2016 17:26, Jerin Jacob wrote: > >On Tue, Jan 26, 2016 at 05:25:50PM +, David Hunt wrote: > >>Hi all on the list. > >> > >>Here's a proposed patch for an external mempool manager > >> > >>The External Mempool Manager is an

[dpdk-dev] [RFC PATCH 0/2] Fix examples/distributor build issue for non x86

On Fri, Jan 29, 2016 at 08:03:37AM -0700, Bruce Richardson wrote: > On Fri, Jan 29, 2016 at 08:51:41AM +0530, Jerin Jacob wrote: > > On Sun, Dec 06, 2015 at 08:54:28PM +0530, Jerin Jacob wrote: > > > Introduced rte_prefetch_non_temporal() to remove IA specific > > > _mm_prefect(addr, 0) > > > gcc

[dpdk-dev] [PATCH] example/ipsec-secgw: ipsec security gateway

Sample app implementing an IPsec Security Geteway. The main goal of this app is to show the use of cryptodev framework in a real world application. Currently only supported static IPv4 IPsec tunnels using AES-CBC and HMAC-SHA1. Also, currently not supported: - SA auto negotiation (No IKE

[dpdk-dev] Increasing the number of traffic classes

Hi, I know that this topic have been covered in the youtube video and mailing list (http://dpdk.org/ml/archives/dev/2015-June/018875.html ) in the past. The solution suggested was to have 4 queues per traffic classes and each of those

[dpdk-dev] [PATCH] eal: make resource initialization more robust

Current issue: DPDK is not that friendly to container environment, which caused by that it pre-alloc resource like cores and hugepages. But there are this or that resource limitations, for examples, cgroup, rlimit, cpuset, etc. For cores, this patch makes use of pthread_getaffinity_np to further

[dpdk-dev] Errors Rx count increasing while pktgen doing nothing on Intel 82598EB 10G

Let me share one more information about this issue. I tried to run dpdk-2.2.0/examples/ethtool, which showed the same problem. (i.e. I guess other examples will also fail.) [root at centos7 app]# ./ethtool EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 0 on socket 1

[dpdk-dev] [PATCH] examples: l3fwd exact-match path rework

Current implementation of Exact-Match uses different execution path than for LPM. Unifying them allows to reuse big part of LPM code and sightly increase performance of Exact-Match. Main changes: - * Packet classification stage is separated from the rest of path for both LPM and EM.

[dpdk-dev] [PATCH 0/3] null driver improvements for testability

Hi Paul, 2016-01-29 16:18, Paul Atkins: > This patchset adds functionality to the null driver help when testing > a dataplane that uses dpdk. The idea is that the the dataplane can > have multiple null interfaces attached, and each of theses can be > assigned a mac address. Packets can then be

[dpdk-dev] [PATCH v2 3/3] virtio: Add a new layer to abstract pci access method

On Thu, Jan 28, 2016 at 06:33:32PM +0900, Tetsuya Mukawa wrote: > This patch addss function pointers to abstract pci access method. > This abstraction layer will be used when virtio-net PMD supports > container extension. > > The below functions abstract how to access to pci configuration space.

[dpdk-dev] [PATCH v7 3/5] ethdev: redesign link speed config API

Hi Marc, On Fri, Jan 29, 2016 at 01:42:05AM +0100, Marc Sune wrote: >[...] > /** > - * Device supported speeds > - */ > -#define ETH_SPEED_CAP_NOT_PHY(0) /*< No phy media > */ > -#define ETH_SPEED_CAP_10M_HD (1 << 0) /*< 10 Mbps half-duplex> */ > -#define ETH_SPEED_CAP_10M_FD (1 << 1)

[dpdk-dev] [PATCH 3/3] null: remove duplicate fields in internal data struct

1- remove duplicate nb_rx/tx_queues fields from internals 2- remove duplicate numa_node field from internals Signed-off-by: Ferruh Yigit --- drivers/net/null/rte_eth_null.c | 36 1 file changed, 12 insertions(+), 24 deletions(-) diff --git

[dpdk-dev] [PATCH 2/3] ring: remove duplicate fields in internal data struct

1- Remove duplicate nb_rx/tx_queues fields from internals 2- Remove data->rx/tx_queues allocation, whose auto allocated by libether 3- Remove duplicate data->rx/tx_queues[i] assignments Signed-off-by: Ferruh Yigit --- drivers/net/ring/rte_eth_ring.c | 52

[dpdk-dev] [PATCH 1/3] pcap: remove duplicate fields in internal data struct

1- Remove duplicate nb_rx/tx_queues fields from internals 2- Move duplicate code into a common function Signed-off-by: Ferruh Yigit --- drivers/net/pcap/rte_eth_pcap.c | 130 +++- 1 file changed, 61 insertions(+), 69 deletions(-) diff --git

[dpdk-dev] [PATCH 0/3] clean-up on virtual PMDs

This is a clean-up patch, no defect fixed, no functional difference expected. Patch mainly removes duplicated fields between data->dev_private and data (struct rte_eth_dev_data). There are a few minor cleanups that: pcap: move a common code into a function ring: remove duplicated

[dpdk-dev] [PATCH v5 09/11] virtio_pci: do not parse if interface is vfio-noiommu

On Fri, Jan 29, 2016 at 10:02:26AM +0100, Thomas Monjalon wrote: > 2016-01-29 15:34, Yuanhan Liu: > > There is another option for that: the git scissors option; you could > > check the git format-patch man page for more detailed info (by searching > > "scissors" keyword). I'm just not quite sure

[dpdk-dev] [RFC PATCH 5/5] virtio: Extend virtio-net PMD to support container environment

On Fri, Jan 29, 2016 at 04:57:23PM +0800, Yuanhan Liu wrote: > On Thu, Jan 21, 2016 at 08:07:58PM +0900, Tetsuya Mukawa wrote: > > +static int > > +virt_read_pci_cfg(struct virtio_hw *hw, void *buf, size_t len, off_t > > offset) > > +{ > > + qtest_read_pci_cfg(hw, "virtio-net", buf, len,

[dpdk-dev] [PATCH 0/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA)

2016-01-29 16:42, Jan M?dala: > Hello Thomas, > > 2016-01-28 16:40 GMT+01:00 Thomas Monjalon : > > > > lib/librte_eal/linuxapp/ena_uio/ena_uio_driver.c | 276 +++ > > > > Sorry the kernel module party is over. > > One day, igb_uio will be removed. > > I suggest to make a first version without

[dpdk-dev] [RFC PATCH 5/5] virtio: Extend virtio-net PMD to support container environment

On Thu, Jan 21, 2016 at 08:07:58PM +0900, Tetsuya Mukawa wrote: > +static int > +virt_read_pci_cfg(struct virtio_hw *hw, void *buf, size_t len, off_t offset) > +{ > + qtest_read_pci_cfg(hw, "virtio-net", buf, len, offset); > + return 0; > +} > + > +static void * >

[dpdk-dev] [PATCH 0/3] null driver improvements for testability

Hi Thomas, On 29/01/16 16:31, Thomas Monjalon wrote: > Hi Paul, > > 2016-01-29 16:18, Paul Atkins: >> This patchset adds functionality to the null driver help when testing >> a dataplane that uses dpdk. The idea is that the the dataplane can >> have multiple null interfaces attached, and each of

[dpdk-dev] [PATCH 0/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA)

Hello Thomas, 2016-01-28 16:40 GMT+01:00 Thomas Monjalon : > > lib/librte_eal/linuxapp/ena_uio/ena_uio_driver.c | 276 +++ > > Sorry the kernel module party is over. > One day, igb_uio will be removed. > I suggest to make a first version without interrupt support > and work with Linux

[dpdk-dev] [PATCH v2 1/1] jobstats: added function abort for job

This patch adds new function rte_jobstats_abort. It marks *job* as finished and time of this work will be add to management time instead of execution time. This function should be used instead of rte_jobstats_finish if condition occurs, condition is defined by the application for example when

[dpdk-dev] [PATCH 3/3] null: add xstats to provide the number of rx polls

When using the null driver and passing in packets via the rx ring, it is useful to know that the driver has polled the ring. Add a count of rx polls to the xstats to provide this information. Signed-off-by: Paul Atkins --- drivers/net/null/rte_eth_null.c | 70

[dpdk-dev] [PATCH 2/3] null: add rings to allow user to provide the mbufs for rx/tx

When using the null driver it is useful to be able to provide a set of mbufs to be received on the interface. Add an option to specify a ring that the driver can poll to provide the set of packets that have been received. Add a similar ring for the tx side where the packets that are being

[dpdk-dev] [PATCH 1/3] null: add a new arg to allow users to specify ether address

Add a new argument to the null driver to allow the user to specify the ether address to be used instead of the default which is all zeroes. This also allows the user to specify an address per device instead of them all using the same default one. Signed-off-by: Paul Atkins ---

[dpdk-dev] [PATCH 0/3] null driver improvements for testability

This patchset adds functionality to the null driver help when testing a dataplane that uses dpdk. The idea is that the the dataplane can have multiple null interfaces attached, and each of theses can be assigned a mac address. Packets can then be injected into the null drivers by adding them to a

[dpdk-dev] [PATCH 2/2] kdp: add virtual PMD for kernel slow data path communication

On Thu, Jan 28, 2016 at 08:16:09AM +, Xu, Qian Q wrote: > Any dependencies with kernel versions? What kernel versions should it > support? > Hi Qian, Kernel module dependencies is same as KNI, and DPDK supports Kernel version >= 2.6.34, this is valid for KDP. For PMD, it is not dependent

[dpdk-dev] [PATCH v2 9/9] pci: implement automatic bind/unbind

Reuse pci hook to implement automatic bind / unbind. The more I look at this, the more I think this should go to the PMDs themselves (with options per devices to control this), with EAL offering helpers to achieve this. Signed-off-by: David Marchand --- lib/librte_eal/bsdapp/eal/eal_pci.c

[dpdk-dev] [PATCH v2 8/9] pci: implement blacklist using a hook

The idea is to prepare a generic hook system for all bus, but I am still unsure if this approach will be the right one, hence, keeping this as private for now. Here, blacklisting policy is removed from pci scan code, making it possible to override it later by the application (once the api is

[dpdk-dev] [PATCH v2 7/9] pci: remove driver lookup from detach

A device is linked to a driver at probe time. When detaching, we should call this same driver detach() function and no need for a driver lookup. Signed-off-by: David Marchand --- Changes since v1: - moved some logs for consistency --- lib/librte_eal/common/eal_common_pci.c | 19

[dpdk-dev] [PATCH v2 6/9] pci: factorize driver search

Same idea as a few commits before, no need to implement the same logic in probe and detach functions. Here, the driver matching is done by a helper, then probe / detach functions are called respectively. Signed-off-by: David Marchand --- lib/librte_eal/common/eal_common_pci.c | 96

[dpdk-dev] [PATCH v2 5/9] pci: cosmetic change

Indent previous commit, rename functions (internal and local functions do not need rte_eal_ prefix). Signed-off-by: David Marchand --- lib/librte_eal/common/eal_common_pci.c | 106 - 1 file changed, 52 insertions(+), 54 deletions(-) diff --git

[dpdk-dev] [PATCH v2 4/9] pci: factorize probe/detach code

Move pci id matching to a helper and reuse it in probe and detach functions. Signed-off-by: David Marchand --- lib/librte_eal/common/eal_common_pci.c | 67 -- 1 file changed, 23 insertions(+), 44 deletions(-) diff --git a/lib/librte_eal/common/eal_common_pci.c

[dpdk-dev] [PATCH v2 3/9] pci/linux: rework sysfs parsing for driver

There is no use for pci_get_kernel_driver_by_path() apart recognising kernel driver and fill kdrv field. Signed-off-by: David Marchand --- Changes since v1: - updated the commitlog, Huawei already did the "unknown" -> "none" change, so this patch ends up just refactoring code ---

[dpdk-dev] [PATCH v2 2/9] pci/linux: minor cleanup

Those are the only fields that are explicitly set to 0 while the global dev pointer is set to 0 a few lines before. Signed-off-by: David Marchand --- lib/librte_eal/linuxapp/eal/eal_pci.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git

[dpdk-dev] [PATCH v2 1/9] pci: add internal device list helpers

Remove duplicate code by moving this to helpers in common. Signed-off-by: David Marchand --- Changes since v1: - moved helpers to eal_private.h --- lib/librte_eal/bsdapp/eal/eal_pci.c| 34 --- lib/librte_eal/common/eal_common_pci.c | 76 --

[dpdk-dev] [PATCH v2 0/9] pci cleanup and blacklist rework

Before 2.2.0 release, while preparing for more changes in eal (and fixing a problem reported by Roger M. [1]), I came up with this (part of) patchset that tries to make the pci code more compact and easier to read. I ended up introducing some hooks in the pci layer to customize pci blacklist /

[dpdk-dev] [PATCH] ixgbe: fix x550 VF tx issue

On x550, the basic tx function may not work if we use DPDK VF based on kernel PF. The reason is kernel PF enables a new feature "malicious driver detection". According to this feature, driver should create TX context descriptor and set the "Check Context" bit in advanced data descriptor. This

[dpdk-dev] [PATCH v3 0/4] fix the issue that DPDK takes over virtio device blindly

On Wed, Jan 27, 2016 at 11:21:18PM +0800, Huawei Xie wrote: > v3 changes: > change log message to tell user that the virtio device is skipped > due to it is managed by kernel driver, instead of asking user to > unbind it from kernel driver. > > v2 changes: > Remove unnecessary assignment of

[dpdk-dev] [PATCH v5 10/11] virtio: pci: add dummy func definition for in/outb for non-x86 arch

On Fri, Jan 29, 2016 at 01:01:02PM +0530, Santosh Shukla wrote: > > Another generic comment about this patchset is that it VERY okay to > > include several components change in one set, but putting them in > > order helps review a lot. > > > > Say, this patch set has dependence on VFIO stuff,

[dpdk-dev] [PATCH v5 09/11] virtio_pci: do not parse if interface is vfio-noiommu

On Fri, Jan 29, 2016 at 12:52:53PM +0530, Santosh Shukla wrote: > On Fri, Jan 29, 2016 at 12:47 PM, Yuanhan Liu > wrote: > > Two minor nits. > > > > Firstly about your title, you should be consistent: sometimes you > > use virtio_pci, and sometimes you use virtio_pic.h. And for virtio > > pmd

[dpdk-dev] [PATCH 3/4] lib/librte_port: add packet dumping to PCAP file support in sink port

Hi Panu, Thank you again for careful review and comments. On 28/01/2016 11:43, Panu Matilainen wrote: > On 01/27/2016 07:39 PM, Fan Zhang wrote: >> Originally, sink ports in librte_port releases received mbufs back to >> mempool. This patch adds optional packet dumping to PCAP feature in sink >>

[dpdk-dev] [PATCH v7 1/2] tools: Add support for handling built-in kernel modules

On Thu, Jan 28, 2016 at 02:13:53PM +0100, krytarowski at caviumnetworks.com wrote: > From: Kamil Rytarowski > > Currently dpdk_nic_bind.py detects Linux kernel modules via reading > /proc/modules. Built-in ones aren't listed there and therefore they are not > being found by the script. > > Add

[dpdk-dev] [PATCH v5 09/11] virtio_pci: do not parse if interface is vfio-noiommu

Two minor nits. Firstly about your title, you should be consistent: sometimes you use virtio_pci, and sometimes you use virtio_pic.h. And for virtio pmd driver, "virtio: " prefix is pretty enough, no need another extra "vfio: " or "pci: " prefix. And the same to your EAL changes. EAL is a

[dpdk-dev] [PATCH 1/4] lib/librte_port: add PCAP file support to source port

Hi Panu, Thank you for the careful review and comments. On 28/01/2016 11:54, Panu Matilainen wrote: > On 01/27/2016 07:39 PM, Fan Zhang wrote: >> Originally, source ports in librte_port is an input port used as packet >> generator. Similar to Linux kernel /dev/zero character device, it >>

[dpdk-dev] [PATCH 9/9] eal: relocate hotplug code from ethdev

hotplug which deals with resources should come from the layer that already handles them, i.e. eal. Signed-off-by: David Marchand --- lib/librte_eal/bsdapp/eal/rte_eal_version.map | 8 + lib/librte_eal/common/eal_common_dev.c | 39 lib/librte_eal/common/eal_common_pci.c

[dpdk-dev] [PATCH 8/9] pci: add a helper to refresh a device

It will be used mainly for hotplug code. Signed-off-by: David Marchand --- lib/librte_eal/bsdapp/eal/eal_pci.c | 49 +++ lib/librte_eal/common/eal_private.h | 13 ++ lib/librte_eal/linuxapp/eal/eal_pci.c | 13 ++ 3 files changed, 75

[dpdk-dev] [PATCH 7/9] pci: add a helper for device name

eal is a better place than ethdev for naming resources. Add a helper here, and make use of it in ethdev hotplug code. Signed-off-by: David Marchand --- lib/librte_eal/common/include/rte_pci.h | 28 lib/librte_ether/rte_ethdev.c | 22 ++

[dpdk-dev] [PATCH 6/9] eal: initialize vdevs right next to pci devices

This way, the resources probing happens in a common place. Signed-off-by: David Marchand --- lib/librte_eal/bsdapp/eal/eal.c | 7 +++ lib/librte_eal/common/include/rte_dev.h | 2 +- lib/librte_eal/linuxapp/eal/eal.c | 7 +++ 3 files changed, 15 insertions(+), 1 deletion(-)

[dpdk-dev] [PATCH 5/9] eal: get rid of pmd type

Now that we only have vdev drivers, there is no need for a pmd type in rte_driver. rte_driver is now purely a vdev thing, and could be renamed later (then .init would become .probe, .uninit would become .remove). Signed-off-by: David Marchand --- drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 2

[dpdk-dev] [PATCH 4/9] eal/linux: move back interrupt thread init before setting affinity

Now that virtio pci driver is initialized in a constructor, we only need to move the interrupt thread init after loading the plugins. This way, chelsio driver should be happy again [1]. [1] http://dpdk.org/ml/archives/dev/2015-November/028289.html Signed-off-by: David Marchand ---

[dpdk-dev] [PATCH 3/9] drivers: no more pdev drivers

Now that pdev drivers have been converted to pci drivers, there is nothing left in their init functions that can't go in a constructor. pdev / vdev drivers init order is changed by this commit, but I can't see why we would need to preserve it. Signed-off-by: David Marchand ---

[dpdk-dev] [PATCH 2/9] pci: register all pdev as pci drivers

pdev drivers are actually pci drivers. Wrappers for ethdev and crypto pci drivers, that assume a 1 to 1 association between pci device and upper device, have been added so that current drivers are not impacted. Signed-off-by: David Marchand --- drivers/crypto/qat/rte_qat_cryptodev.c |

[dpdk-dev] [PATCH 1/9] pci: no need for dynamic tailq init

These lists can be initialized once and for all at build time. With this, those lists are only manipulated in a common place (and we could even make them private). A nice side effect is that pci drivers can now register in constructors. Signed-off-by: David Marchand ---

[dpdk-dev] [PATCH 0/9] prepare for rte_device / rte_driver

Following discussions with Jan [1] and some cleanup I started on pci code, here is a patchset that reworks pdev drivers registration and hotplug api. The structures changes mentioned in [1] are still to be done, but at least, I think we are one step closer to it. Before this patchset, rte_driver

[dpdk-dev] [PATCH v5 06/11] virtio: vfio: add api support to rd/wr ioport bar

On Tue, Jan 19, 2016 at 05:16:07PM +0530, Santosh Shukla wrote: > For vfio case - Use pread/pwrite api to access virtio > ioport space. > > Applicable for virtio 0.95 spec. > > Signed-off-by: Santosh Shukla > Signed-off-by: Rizwan Ansari > Signed-off-by: Rakesh Krishnamurthy > --- > v4 -->

[dpdk-dev] [PATCH v7 5/5] ethdev: add rte_eth_speed_to_bm_flag() to ver. map

On 01/29/2016 02:42 AM, Marc Sune wrote: > Added rte_eth_speed_to_bm_flag() to DPDK2.2 version map. > > Signed-off-by: Marc Sune > --- > lib/librte_ether/rte_ether_version.map | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git a/lib/librte_ether/rte_ether_version.map >

[dpdk-dev] [PATCH 8/8] doc: add release note for E-tag

Signed-off-by: Wenzhuo Lu --- doc/guides/rel_notes/release_2_3.rst | 6 ++ 1 file changed, 6 insertions(+) diff --git a/doc/guides/rel_notes/release_2_3.rst b/doc/guides/rel_notes/release_2_3.rst index 99de186..16bd80b 100644 --- a/doc/guides/rel_notes/release_2_3.rst +++

[dpdk-dev] [PATCH 7/8] app/testpmd: add CLIs for E-tag operation

Add the CLIs to support the E-tag operation. 1, Offloading of E-tag insertion and stripping. 2, Forwarding the E-tag packets to pools based on the GRP and E-CID_base. Signed-off-by: Wenzhuo Lu --- app/test-pmd/cmdline.c | 340 + 1 file changed,

[dpdk-dev] [PATCH 6/8] ixgbe: support l2 tunnel operation

Add support of l2 tunnel operation. Support enabling/disabling l2 tunnel tag insertion/stripping. Support enabling/disabling l2 tunnel packets forwarding. Support adding/deleting forwarding rules for l2 tunnel packets. Only support E-tag now. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH 5/8] lib/librte_ether: support new l2 tunnel operation

Add functions to support the new l2 tunnel operation. 1, Insertion and stripping for l2 tunnel tag. 2, Forwarding the packets to a pool based on l2 tunnel tag. Signed-off-by: Wenzhuo Lu --- lib/librte_ether/rte_ethdev.c | 178 lib/librte_ether/rte_ethdev.h |

[dpdk-dev] [PATCH 4/8] app/testpmd: add CLIs for l2 tunnel config

Add CLIs to config ether type of l2 tunnel, and to enable/disable a type of l2 tunnel. Now only e-tag tunnel is supported. Signed-off-by: Wenzhuo Lu --- app/test-pmd/cmdline.c | 259 + 1 file changed, 259 insertions(+) diff --git

[dpdk-dev] [PATCH 3/8] ixgbe: support l2 tunnel config

Add support of l2 tunnel configuration. Support modifying ether type of a type of l2 tunnel. Support enabling and disabling the support of a type of l2 tunnel. Only E-tag tunnel is supported now. Signed-off-by: Wenzhuo Lu --- drivers/net/ixgbe/ixgbe_ethdev.c | 140

[dpdk-dev] [PATCH 2/8] lib/librte_ether: support l2 tunnel config

Add functions to support l2 tunnel configuration. The support includes ether type modification and the tunnel support enabling/disabling. Ether type modification means modifying the ether type of a specific type of tunnel. So the packet with this ether type will be parsed as this type of tunnel.

[dpdk-dev] [PATCH 1/8] ixgbe: select pool by MAC when using double VLAN

On X550, as required by datasheet, E-tag packets are not expected when double VLAN are used. So modify the register PFVTCTL after enabling double VLAN to select pool by MAC but not MAC or E-tag. Signed-off-by: Wenzhuo Lu --- drivers/net/ixgbe/ixgbe_ethdev.c | 10 ++ 1 file changed, 10

[dpdk-dev] [PATCH 0/8] support E-tag offloading and forwarding on Intel X550 NIC

This patch set adds the support of E-tag offloading and forwarding on X550. The offloading means E-tag can be inserted and stripped by HW. And E-tag packets can be recognized and forwarded to specific pools based on GRP and E-CID_base in E-tag. Wenzhuo Lu (8): ixgbe: select pool by MAC when

[dpdk-dev] [PATCH v5 10/11] virtio: pci: add dummy func definition for in/outb for non-x86 arch

On Tue, Jan 19, 2016 at 05:16:11PM +0530, Santosh Shukla wrote: > For non-x86 arch, Compiler will throw build error for in/out apis. Including > dummy api function so to pass build. > > Note that: For virtio to work for non-x86 arch - RTE_EAL_VFIO is the only > supported method. RTE_EAL_IGB_UIO

[dpdk-dev] [PATCH v4 00/14] Add virtio support for arm/arm64

On Fri, Jan 29, 2016 at 12:57 PM, Xie, Huawei wrote: > On 1/14/2016 9:29 PM, Santosh Shukla wrote: >> Hi, >> >> This v4 patch uses vfio-noiommu-way to access virtio-net pci interface. >> Tested for arm64 thunderX platform. Patch builds for >> x86/i386/arm/armv8/thunderX. Tested with testpmd

[dpdk-dev] [PATCH] pci: Add the class_id support in pci probe

On 01/29/2016 12:10 PM, Panu Matilainen wrote: > On 01/29/2016 11:34 AM, Thomas Monjalon wrote: >> 2016-01-29 11:21, Panu Matilainen: >>> On 01/28/2016 11:38 PM, Thomas Monjalon wrote: 2016-01-13 14:22, Panu Matilainen: > On 01/13/2016 01:55 PM, Bruce Richardson wrote: >> On Thu, Dec

[dpdk-dev] [PATCH v5 09/11] virtio_pci: do not parse if interface is vfio-noiommu

On Fri, Jan 29, 2016 at 2:32 PM, Thomas Monjalon wrote: > 2016-01-29 15:34, Yuanhan Liu: >> There is another option for that: the git scissors option; you could >> check the git format-patch man page for more detailed info (by searching >> "scissors" keyword). I'm just not quite sure Thomas like

[dpdk-dev] [PATCH] pmd/snow3g: add new SNOW 3G SW PMD

Added new SW PMD which makes use of the libsso SW library, which provides wireless algorithms SNOW 3G UEA2 and UIA2 in software. This PMD supports cipher-only, hash-only and chained operations ("cipher then hash" and "hash then cipher") of the following algorithms: -

[dpdk-dev] [PATCH v2] ixgbe: Fix disable interrupt twice

Currently, ixgbe vf and pf will disable interrupt twice in stop stage and uninit stage. It will cause an error: testpmd> quit Shutting down port 0... Stopping ports... Done Closing ports... EAL: Error disabling MSI-X interrupts for fd 26 Done Becasue the interrupt

[dpdk-dev] [PATCH] ixgbe: Fix disable interrupt twice

Currently, ixgbe vf and pf will disable interrupte twice in stop stage and uninit stage. It will cause an error: testpmd> quit Shutting down port 0... Stopping ports... Done Closing ports... EAL: Error disabling MSI-X interrupts for fd 26 Done Becasue the interrupt

[dpdk-dev] [PATCH v7 3/5] ethdev: redesign link speed config API

On 29 January 2016 at 11:17, Ananyev, Konstantin < konstantin.ananyev at intel.com> wrote: > > > > -Original Message- > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > Sent: Friday, January 29, 2016 9:54 AM > > To: Ananyev, Konstantin > > Cc: dev at dpdk.org; Marc Sune;

[dpdk-dev] [PATCH 0/5] add external mempool manager

On 28/01/2016 17:26, Jerin Jacob wrote: > On Tue, Jan 26, 2016 at 05:25:50PM +, David Hunt wrote: >> Hi all on the list. >> >> Here's a proposed patch for an external mempool manager >> >> The External Mempool Manager is an extension to the mempool API that allows >> users to add and use an

[dpdk-dev] [PATCH] eal: Initial implementation of PQoS EAL extension

EAL extension allows CAT and CDP technologies to be configured via "--l3ca*" parameters. Reworking existing applications to make use of DPDK PQoS library is a heavy lift. This EAL extension is to make it easier by adding new command line options. These new options allow to leverage CAT and CDP

[dpdk-dev] [PATCH] lib: Initial implementation of PQoS lib with CAT and CDP support

Please see initial implementation of DPDK PQoS library which enables Cache Allocation Technology (CAT) and its extension, Code Data Prioritization (CDP). Current library version uses MSR registers to program these technologies. This is due to lack of broad enabling in OS frameworks. As the OS

[dpdk-dev] [PATCH v4 4/4] cache/slow-path: reduce cache align requirement for 128-byte cache targets

slow-path data structures need not be 128-byte cache aligned. Reduce the alignment to 64-byte to save the memory. No behavior change for 64-byte cache aligned systems as minimum cache line size as 64. Signed-off-by: Jerin Jacob Acked-by: Konstantin Ananyev --- lib/librte_ether/rte_ethdev.h |

[dpdk-dev] [PATCH v4 3/4] bitmap: optimize for 128-bytes cache line targets

existing rte_bitmap library implementation optimally configured to run on 64-bytes cache line, extending to 128-bytes cache line targets. Signed-off-by: Jerin Jacob --- lib/librte_sched/rte_bitmap.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[dpdk-dev] [PATCH v4 2/4] mbuf: fix performance/cache resource issue with 128-byte cache line targets

No need to split mbuf structure to two cache lines for 128-byte cache line size targets as it can fit on a single 128-byte cache line. Signed-off-by: Jerin Jacob --- app/test/test_mbuf.c | 2 +-

[dpdk-dev] [PATCH v4 1/4] eal: Introduce new cache line macro definitions

- RTE_CACHE_LINE_MIN_SIZE(Supported minimum cache line size) - __rte_cache_min_aligned(Force minimum cache line alignment) - RTE_CACHE_LINE_SIZE_LOG2(Express cache line size in terms of log2) Signed-off-by: Jerin Jacob Suggested-by: Konstantin Ananyev ---

[dpdk-dev] [PATCH v4 0/4] fix performance/cache resource issues with 128-byte cache line targets

This patchset fixes performance/cache resource issues with 128-byte cache line targets found in mbuf and bitmap DPDK libraries Currently, we have two DPDK targets(ThunderX and ppc_64) which are based on 128-bytes cache line size target. This patchset doesn't introduce any performance

[dpdk-dev] [PATCH 2/2] examples: update to use new lpm lib for ip4

Update other applications to use new structures from LPM library for IPv4. Signed-off-by: Michal Kobylinski --- examples/ip_fragmentation/main.c| 23 ++- examples/ip_reassembly/main.c | 22 +++ examples/l3fwd-power/main.c |

[dpdk-dev] [PATCH v2 1/2] lpm: extend ip4 next_hop and add config structure

As next_hop field for IPv4 is increased now the maximum number of tbl8s is 2^24. A new rte_lpm_config structure is used so LPM library will allocate exactly the amount of memory which is necessary to hold application?s rules. Changed structures in LPM library: rte_lpm_tbl24_entry and

[dpdk-dev] [PATCH v2 0/2] Increase number of next hops for LPM IPv4

This patchset extend next_hop field from 8-bits to 24-bits in LPM library for IPv4. As next_hop field is increased now the maximum number of tbl8s is 2^24. A new rte_lpm_config structure is used so LPM library will allocate exactly the amount of memory which is necessary to hold application?s

[dpdk-dev] [PATCH 5/5] doc: update doc for tcpdump feature

Added tcpdump design changes to proc_info section of sample application user guide. Added tcpdump design changes env abstraction layer section of programmers guide. Signed-off-by: Reshma Pattan --- doc/guides/prog_guide/env_abstraction_layer.rst | 29 +++-

[dpdk-dev] [PATCH 4/5] lib/librte_eal: add tcpdump support in primary process

Added tcpdump functionality to eal interrupt thread. Enhanced interrupt thread to support tcpdump socket and message processing from secondary. Created new mempool and rings to handle packets of tcpdump. Added rte_eth_rxtx_callbacks for ingress/egress packets processing for tcpdump. Added

[dpdk-dev] [PATCH 3/5] app/proc_info: add tcpdump support in secondary process

Added "--tcupdump2 and "--src-ip-filter" command line options for tcpdump support. Added pcap device creation and writing of packets to pcap device for tcpdump. Added socket functionality to communicate with primary process. Signed-off-by: Reshma Pattan --- app/proc_info/main.c | 454

[dpdk-dev] [PATCH 2/5] drivers/net/pcap: add public api to create pcap device

Added new public api to create pcap device from pcaps. Added new header file for API declaration. Added new public api to version map Signed-off-by: Reshma Pattan --- drivers/net/pcap/Makefile |4 +- drivers/net/pcap/rte_eth_pcap.c | 156

[dpdk-dev] [PATCH 1/5] app/test-pmd: fix nb_rxq and np_txq checks

Made testpmd changes to validate nb_rxq/nb_txq zero value changes of librte_ether. Signed-off-by: Reshma Pattan --- app/test-pmd/cmdline.c| 11 +-- app/test-pmd/parameters.c | 14 +- app/test-pmd/testpmd.c| 19 +-- 3 files changed, 31

[dpdk-dev] [PATCH 0/5] add dpdk packet capture support for tcpdump

This patch set include design to capture dpdk port packets for tcpdump. This patch set include test-pmd changes to verify patch set given in Dependencies 1. Current patch set is dependent on below patch set. Below patch set must be applied before applying current patch set. Dependencies 1:

[dpdk-dev] [PATCH v5 10/11] virtio: pci: add dummy func definition for in/outb for non-x86 arch

On Fri, Jan 29, 2016 at 12:31 PM, Yuanhan Liu wrote: > On Tue, Jan 19, 2016 at 05:16:11PM +0530, Santosh Shukla wrote: >> For non-x86 arch, Compiler will throw build error for in/out apis. Including >> dummy api function so to pass build. >> >> Note that: For virtio to work for non-x86 arch -

  1   2   >