[dpdk-dev] [PATCH v7 0/5] ethdev: add speed capabilities and refactor link API

The current rte_eth_dev_info abstraction does not provide any mechanism to get the supported speed(s) of an ethdev. For some drivers (e.g. ixgbe), an educated guess could be done based on the driver's name (driver_name in rte_eth_dev_info), see:

[dpdk-dev] [PATCH v7 1/5] ethdev: Added ETH_SPEED_CAP bitmap for ports

Added constants and bitmap to struct rte_eth_dev_info to be used by PMDs. Signed-off-by: Marc Sune --- lib/librte_ether/rte_ethdev.h | 24 1 file changed, 24 insertions(+) diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h index 8710dd7..dbc1599

[dpdk-dev] [PATCH v7 2/5] ethdev: Fill speed capability bitmaps in the PMDs

Added speed capabilities to all pmds supporting physical NICs: * e1000 * ixgbe * i40 * mlx4 * fm10k Signed-off-by: Marc Sune --- drivers/net/e1000/em_ethdev.c| 6 ++ drivers/net/e1000/igb_ethdev.c | 6 ++ drivers/net/fm10k/fm10k_ethdev.c | 4

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

This patch redesigns the API to set the link speed/s configure for an ethernet port. Specifically: - it allows to define a set of advertised speeds for auto-negociation. - it allows to disable link auto-negociation (single fixed speed). - default: auto-negociate all supported speeds. Other

[dpdk-dev] [PATCH v7 4/5] doc: update with link changes

Add new features, ABI changes and resolved issues notice for the refactored link patch. Signed-off-by: Marc Sune --- doc/guides/rel_notes/release_2_3.rst | 26 ++ 1 file changed, 26 insertions(+) diff --git a/doc/guides/rel_notes/release_2_3.rst

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

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 b/lib/librte_ether/rte_ether_version.map index d8db24d..2c14ad7 100644

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

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 intrinsic and build examples/distributor for non 86 platform ping for review. > > Not sure the rte_prefetch_non_temporal mapping correct for

[dpdk-dev] [PATCH v3 0/3] add lpm support for NEON

- This patch enables lpm for ARM - Used architecture agnostic xmm_t to represent 128 bit SIMD variable in rte_lpm_lookupx4 API definition - Tested on Juno and Thunderx boards - Tested and verified the changes with following DPDK unit test cases --lpm_autotest --lpm6_autotest v1..v2

[dpdk-dev] [PATCH v3 1/3] lpm: make rte_lpm_lookupx4 API definition architecture agnostic

-Used architecture agnostic xmm_t to represent 128 bit SIMD variable -Introduced vect_* API abstraction in app/test to test rte_lpm_lookupx4 API in architecture agnostic way -Moved rte_lpm_lookupx4 SSE implementation to architecture specific rte_lpm_sse.h file to accommodate new

[dpdk-dev] [PATCH v3 2/3] lpm: add support for NEON

Enabled CONFIG_RTE_LIBRTE_LPM, CONFIG_RTE_LIBRTE_TABLE, CONFIG_RTE_LIBRTE_PIPELINE libraries for arm and arm64 TABLE, PIPELINE libraries were disabled due to LPM library dependency. Signed-off-by: Jerin Jacob Signed-off-by: Jianbo Liu --- app/test/test_xmmt_ops.h | 20

[dpdk-dev] [PATCH v3 3/3] maintainers: claim responsibility for arm64 specific files of hash and lpm

Signed-off-by: Jerin Jacob --- MAINTAINERS | 3 +++ 1 file changed, 3 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index b90aeea..e3fab58 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -138,6 +138,9 @@ M: Jerin Jacob M: Jianbo Liu F: lib/librte_eal/common/include/arch/arm/*_64.h F:

[dpdk-dev] [PATCH] config: cleanup existing RTE_CACHE_LINE_SIZE selection scheme

On Tue, Dec 08, 2015 at 03:03:34PM +0530, Jerin Jacob wrote: > On Mon, Dec 07, 2015 at 03:45:10PM +0100, Thomas Monjalon wrote: > > 2015-12-07 19:52, Jerin Jacob: > > > by default, all the targets will be configured with the 64-byte cache line > > > size, targets which have different cache line

[dpdk-dev] [PATCH v5 01/11] virtio: Introduce config RTE_VIRTIO_INC_VECTOR

Hi Yuan, On Wed, Jan 27, 2016 at 8:03 AM, Yuanhan Liu wrote: > On Wed, Jan 27, 2016 at 07:53:21AM +0530, Santosh Shukla wrote: >> Ping? > > I was on vacation late last week. And I was quite busy till now after > the vacation. So, sorry that I still don't have time to do more detailed > reviews

[dpdk-dev] [PATCH v5 01/11] virtio: Introduce config RTE_VIRTIO_INC_VECTOR

On Fri, Jan 29, 2016 at 10:02:26AM +0530, Santosh Shukla wrote: > Hi Yuan, It's Yuanhan, but not Yuan :) > On Wed, Jan 27, 2016 at 8:03 AM, Yuanhan Liu > wrote: > > On Wed, Jan 27, 2016 at 07:53:21AM +0530, Santosh Shukla wrote: > >> Ping? > > > > I was on vacation late last week. And I was

[dpdk-dev] [PATCH v5 01/11] virtio: Introduce config RTE_VIRTIO_INC_VECTOR

On Fri, Jan 29, 2016 at 10:12 AM, Yuanhan Liu wrote: > On Fri, Jan 29, 2016 at 10:02:26AM +0530, Santosh Shukla wrote: >> Hi Yuan, > > It's Yuanhan, but not Yuan :) > Sorry for that, >> On Wed, Jan 27, 2016 at 8:03 AM, Yuanhan Liu >> wrote: >> > On Wed, Jan 27, 2016 at 07:53:21AM +0530,

[dpdk-dev] [PATCH v3 0/8] vhost-user live migration support

This patch set adds the vhost-user live migration support. The major task behind that is to log pages we touched during live migration, including used vring and desc buffer. So, this patch set is basically about adding vhost log support, and using it. Another important thing is that you need

[dpdk-dev] [PATCH v3 1/8] vhost: handle VHOST_USER_SET_LOG_BASE request

VHOST_USER_SET_LOG_BASE request is used to tell the backend (dpdk vhost-user) where we should log dirty pages, and how big the log buffer is. This request introduces a new payload: typedef struct VhostUserLog { uint64_t mmap_size; uint64_t mmap_offset; }

[dpdk-dev] [PATCH v3 2/8] vhost: introduce vhost_log_write

Introduce vhost_log_write() helper function to log the dirty pages we touched. Page size is harded code to 4096 (VHOST_LOG_PAGE), and each log is presented by 1 bit. Therefore, vhost_log_write() simply finds the right bit for related page we are gonna change, and set it to 1. dev->log_base

[dpdk-dev] [PATCH v3 3/8] vhost: log used vring changes

Every time we update virtio used ring, we need to log it. And it's been done by a new vhost_log_write() wrapper, vhost_log_used_vring(). Signed-off-by: Yuanhan Liu Signed-off-by: Victor Kaplansky Tested-by: Pavel Fedin --- v3: remove the unnecessary var "addr" iat vhost_log_used_vring() ---

[dpdk-dev] [PATCH v3 4/8] vhost: log vring desc buffer changes

Every time we copy a buf to vring desc, we need to log it. Signed-off-by: Yuanhan Liu Signed-off-by: Victor Kaplansky Tested-by: Pavel Fedin --- lib/librte_vhost/vhost_rxtx.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/lib/librte_vhost/vhost_rxtx.c

[dpdk-dev] [PATCH v3 5/8] vhost: claim that we support GUEST_ANNOUNCE feature

It's actually a feature already enabled in Linux kernel (since v3.5). What we need to do is simply to claim that we support such feature, and nothing else. With that, the guest will send an ARP message after live migration to notify the switches about the new location of migrated VM.

[dpdk-dev] [PATCH v3 6/8] vhost: handle VHOST_USER_SEND_RARP request

While in former patch we enabled GUEST_ANNOUNCE feature, so that the guest OS will broadcast a GARP message after migration to notify the switch about the new location of migrated VM, the thing is that GUEST_ANNOUNCE is enabled since kernel v3.5 only. For older kernel, VHOST_USER_SEND_RARP request

[dpdk-dev] [PATCH v3 7/8] vhost: enable log_shmfd protocol feature

To claim that we support vhost-user live migration support: SET_LOG_BASE request will be send only when this feature flag is set. Besides this flag, we actually need another feature flag set to make vhost-user live migration work: VHOST_F_LOG_ALL. Which, however, has been enabled long time ago.

[dpdk-dev] [PATCH v3 8/8] vhost: remove duplicate header include

unistd.h has been included twice; remove one. Signed-off-by: Yuanhan Liu --- lib/librte_vhost/vhost_user/virtio-net-user.c | 1 - 1 file changed, 1 deletion(-) diff --git a/lib/librte_vhost/vhost_user/virtio-net-user.c b/lib/librte_vhost/vhost_user/virtio-net-user.c index cda330d..4270c98

[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 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 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 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 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 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 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 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 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 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 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 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 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 0/8] support E-tag offloading and forwarding on Intel X550 NIC

Hi, Wenzhuo Better to explain what E-tag is, so that reviewers could known it. Thanks, Michael On 1/29/2016 3:05 PM, Wenzhuo Lu wrote: > 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

[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 v5 06/11] virtio: vfio: add api support to rd/wr ioport bar

On Fri, Jan 29, 2016 at 12:37 PM, Yuanhan Liu wrote: > 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

[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 v4 00/14] Add virtio support for arm/arm64

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 application. Hi Shukla: I would take two week's leave from

[dpdk-dev] [PATCH v2 1/2] i40evf: allocate virtchnl cmd buffer for each vf

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jingjing Wu > Sent: Wednesday, January 27, 2016 9:50 AM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH v2 1/2] i40evf: allocate virtchnl cmd buffer for > each vf > > Currently, i40evf PMD uses a global

[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 -

[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 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 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 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 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 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 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 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] 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 v2] ixgbe: Fix disable interrupt twice

Hi Michael, > -Original Message- > From: Qiu, Michael > Sent: Friday, January 29, 2016 1:58 PM > To: dev at dpdk.org > Cc: Zhou, Danny; Liu, Yong; Liang, Cunming; Lu, Wenzhuo; Qiu, Michael > Subject: [PATCH v2] ixgbe: Fix disable interrupt twice > > Currently, ixgbe vf and pf will

[dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf reset request

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jingjing Wu > Sent: Wednesday, January 27, 2016 9:50 AM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf reset > request > > Interrupt based request of PF reset

[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] [RFC PATCH 5/5] virtio: Extend virtio-net PMD to support container environment

On 1/28/2016 10:44 AM, Tetsuya Mukawa wrote: > On 2016/01/27 19:03, Xie, Huawei wrote: >> On 1/21/2016 7:09 PM, Tetsuya Mukawa wrote: >>> + /* Set BAR region */ >>> + for (i = 0; i < NB_BAR; i++) { >>> + switch (dev->bar[i].type) { >>> + case QTEST_PCI_BAR_IO: >>> +

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

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 it or not. For simple discussions, patch after scissors may

[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 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] [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 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 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/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 31, 2015 at 09:12:14AM -0800, Stephen Hemminger wrote: On Tue, 29 Dec 2015 10:53:26 +0800 Ziye Yang wrote: > This patch is used

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

Hi Marc, > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Marc Sune > Sent: Friday, January 29, 2016 12:42 AM > To: dev at dpdk.org; Lu, Wenzhuo; Zhang, Helin; Harish Patil; Chen, Jing D > Subject: [dpdk-dev] [PATCH v7 3/5] ethdev: redesign link speed config

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

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 31, 2015 at 09:12:14AM -0800, Stephen Hemminger wrote: > On Tue, 29 Dec 2015 10:53:26 +0800 >

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

2016-01-29 09:24, Ananyev, Konstantin: > Can you avoid modifications in the e1000/base code? > We do not modify (and maintain) that part on our own. > Instead we take it straight from Intel ND. > So if you feel like these changes are really necessary - please submit a patch > to ND first, and if

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

Hi Thomas, > -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Friday, January 29, 2016 9:38 AM > To: Ananyev, Konstantin > Cc: dev at dpdk.org; Marc Sune; Lu, Wenzhuo; Zhang, Helin; Harish Patil; > Chen, Jing D; Mcnamara, John > Subject: Re:

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

2016-01-29 09:47, Ananyev, Konstantin: > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > 2016-01-29 09:24, Ananyev, Konstantin: > > > Can you avoid modifications in the e1000/base code? > > > We do not modify (and maintain) that part on our own. > > > Instead we take it straight

[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] pci: Add the class_id support in pci probe

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 31, 2015 at 09:12:14AM -0800, Stephen Hemminger wrote:

[dpdk-dev] [PATCH] doc: minor correction in document

* remove outdated chapter reference to Multi-process support Fixes: fc1f2750a3ec ("doc: programmers guide") * html output converts "--" to "-", this is wrong when explaining the command arguments, used "option list" to fix this:

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

> -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; Lu, Wenzhuo; Zhang, Helin; Harish Patil; > Chen, Jing D; Mcnamara, John > Subject: Re: [dpdk-dev]

[dpdk-dev] [PATCH] mlx5: fix header generation in parallel builds

Fixes: 771fa900b73a ("mlx5: introduce new driver for Mellanox ConnectX-4 adapters") Signed-off-by: Adrien Mazarguil --- drivers/net/mlx5/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/mlx5/Makefile b/drivers/net/mlx5/Makefile index ae568e6..698f072

[dpdk-dev] [PATCH 0/5] Add flow director and RX VLAN stripping support

To preserve compatibility with Mellanox OFED 3.1, flow director and RX VLAN stripping code is only enabled if compiled with 3.2. Yaacov Hazan (5): mlx5: refactor special flows handling mlx5: add special flows (broadcast and IPv6 multicast) mlx5: make flow steering rule generator more

[dpdk-dev] [PATCH 1/5] mlx5: refactor special flows handling

From: Yaacov Hazan Merge redundant code by adding a static initialization table to manage promiscuous and allmulticast (special) flows. New function priv_rehash_flows() implements the logic to enable/disable relevant flows in one place from any context. Signed-off-by:

[dpdk-dev] [PATCH 2/5] mlx5: add special flows (broadcast and IPv6 multicast)

From: Yaacov Hazan Until now, broadcast frames were handled like unicast. Moving the related flow to the special flows table frees up the related unicast MAC entry. The same method is used to handle IPv6 multicast frames. Signed-off-by: Yaacov Hazan Signed-off-by: Adrien

[dpdk-dev] [PATCH 3/5] mlx5: make flow steering rule generator more generic

From: Yaacov Hazan Upcoming flow director support will reuse this function to generate filter rules. Signed-off-by: Yaacov Hazan Signed-off-by: Adrien Mazarguil --- drivers/net/mlx5/mlx5_mac.c| 4 ++-- drivers/net/mlx5/mlx5_rxmode.c | 5 +++--

[dpdk-dev] [PATCH 4/5] mlx5: add support for flow director

From: Yaacov Hazan Add support for flow director filters (RTE_FDIR_MODE_PERFECT and RTE_FDIR_MODE_PERFECT_MAC_VLAN modes). This feature requires MLNX_OFED 3.2. Signed-off-by: Yaacov Hazan Signed-off-by: Adrien Mazarguil --- drivers/net/mlx5/Makefile | 6 +

[dpdk-dev] [PATCH 5/5] mlx5: add support for RX VLAN stripping

From: Yaacov Hazan Allows HW to strip the 802.1Q header from incoming frames and report it through the mbuf structure. This feature requires MLNX_OFED >= 3.2. Signed-off-by: Yaacov Hazan Signed-off-by: Adrien Mazarguil --- drivers/net/mlx5/mlx5.c | 16 ++-

[dpdk-dev] [PATCH 0/6] Performance optimizations for mlx5

This patchset improves the mlx5 PMD performance by doing better prefetching, by reordering internal structure fields and by removing a few unnecessary operations. Note: should be applied after "Add flow director and RX VLAN stripping support" to avoid conflicts. Nelio Laranjeiro (6): mlx5:

[dpdk-dev] [PATCH 2/6] mlx5: reorder TX/RX queue structure

From: Nelio Laranjeiro Remove padding and move important fields to the beginning for better performance. Signed-off-by: Nelio Laranjeiro --- drivers/net/mlx5/mlx5_rxtx.h | 31 --- 1 file changed, 16 insertions(+), 15 deletions(-) diff

[dpdk-dev] [PATCH 3/6] mlx5: remove one indirection level from RX/TX functions

From: Nelio Laranjeiro Avoid dereferencing pointers twice to get to fast Verbs functions by storing them directly in RX/TX queue structures. Signed-off-by: Nelio Laranjeiro --- drivers/net/mlx5/Makefile| 1 + drivers/net/mlx5/mlx5_rxq.c | 12

[dpdk-dev] [PATCH 4/6] mlx5: process offload flags only when requested

From: Nelio Laranjeiro Improve performance by processing offloads only when requested by the application. Signed-off-by: Nelio Laranjeiro --- drivers/net/mlx5/mlx5_rxtx.c | 29 - 1 file changed, 16 insertions(+), 13 deletions(-) diff

[dpdk-dev] [PATCH 5/6] mlx5: avoid lkey retrieval for inlined packets

From: Nelio Laranjeiro Improves performance as the lkey is not needed by hardware in this case. Signed-off-by: Nelio Laranjeiro --- drivers/net/mlx5/mlx5_rxtx.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git

[dpdk-dev] [PATCH 6/6] mlx5: free buffers immediately after completion

From: Nelio Laranjeiro This lowers the amount of cache misses. Signed-off-by: Nelio Laranjeiro --- drivers/net/mlx5/mlx5_rxtx.c | 35 --- 1 file changed, 20 insertions(+), 15 deletions(-) diff --git a/drivers/net/mlx5/mlx5_rxtx.c

[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 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 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 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] 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 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 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 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 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 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 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] 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] 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

  1   2   >