[dpdk-dev] [PATCH]Upgrade NIC share codes: fix a compilation error when RTE_NIC_BYPASS=y

2014-05-29 16:47, Jijiang Liu: > There is a compilation error using latest NIC share codes when > RTE_NIC_BYPASS=y, the root cause is that the setup_link API have already > changed in the share codes, so change > ixgbe_setup_mac_link_multispeed_fixed_fiber() for eliminating the > compilation error.

[dpdk-dev] [PATCH 0/3] *** Upgrade NIC share codes ***

Hi Jijiang, 2014-05-27 01:51, Liu, Jijiang: > This is a batch update of the code in DPDK to align it with the latest > versions of the common device driver code for Intel network devices, such > as is used in the Linux and BSD drivers. Intel DPDK team get periodic > updates from the networking div

[dpdk-dev] [PATCH 4/4] i40e: remove endian.h include

endian.h is not needed for the compilation of i40e_rxtx.c and its inclusion prevents building on FreeBSD systems. Signed-off-by: Bruce Richardson --- lib/librte_pmd_i40e/i40e_rxtx.c | 1 - 1 file changed, 1 deletion(-) diff --git a/lib/librte_pmd_i40e/i40e_rxtx.c b/lib/librte_pmd_i40e/i40e_rxtx

[dpdk-dev] [PATCH 3/4] scripts: fix filtering of comments on bsd

On BSD 10, the cpp binary behaves a little differently and often leaves lines starting with a space before the inital '#' character. This change ensures those lines are filtered out properly. Signed-off-by: Bruce Richardson --- scripts/gen-config-h.sh | 2 +- 1 file changed, 1 insertion(+), 1 de

[dpdk-dev] [PATCH 2/4] test app: remove unused variable definition

Remove an unused variable definition in test_table_acl.c Signed-off-by: Bruce Richardson --- app/test/test_table_acl.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/app/test/test_table_acl.c b/app/test/test_table_acl.c index afc234a..ad0e6f1 100644 --- a/app/test/test_table_acl.c +++ b/ap

[dpdk-dev] [PATCH 1/4] testpmd: fix commandline variable types

A number of commandline entries in the testpmd commandline were actually defined as being string type values when in fact they were being initialized as integer types. Correct this by specifying them as integer type values in the type definition. Signed-off-by: Bruce Richardson --- app/test-pmd/

[dpdk-dev] [PATCH 0/4] minor fixes from BSD and clang testing

When testing compilation on BSD systems and with the clang compiler a number of minor issues were encountered. This patchset fixes some of these. NOTE: compilation targets for using clang on BSD and Linux I'm planning to upstream post-1.7 release. These are just issues found when doing testing fo

[dpdk-dev] Testing memnic for VM to VM transfer

Thanks guys, I will try. -Original Message- From: Hiroshi Shimamoto [mailto:h-shimam...@ct.jp.nec.com] Sent: Wednesday, June 18, 2014 8:06 PM To: Thomas Monjalon; GongJinrong Cc: dev at dpdk.org; 'John Joyce (joycej)'; Olivier MATZ Subject: RE: [dpdk-dev] Testing memnic for VM to VM trans

[dpdk-dev] ##freemail## RE: Testing memnic for VM to VM transfer

Hi, Hiroshi Do you mean I must use DPDK vSwitch in host when I use MEMNIC PMD in guest VM? actually, I just want a channel which can put the data from host to guest quickly. Do you have any idea that how to write a host application to put the data to guest memnic PMD? -Original Message

[dpdk-dev] Testing memnic for VM to VM transfer

Hi, Hiroshi I just start to learn DPDK and memnic, in memnic guide, you said "On host, the shared memory must be initialized by an application using memnic", I am not so clear that how to initialize the share memory in host, do you means use posix API or DPDK API to create the share memory?(it

[dpdk-dev] [PATCH v3] cpu_layout.py: adjust output format to align

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Shannon Zhao > Sent: Wednesday, June 18, 2014 5:18 AM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH v3] cpu_layout.py: adjust output format to align > > Bug: when "core id" is greater than 9, the cpu_layout

[dpdk-dev] [PATCH] dpdk_nic_bind: unbind ports that were erroneously bound

When binding devices to a generic driver (i.e. one that doesn't have a PCI ID table, some devices that are not bound to any other driver could be bound even if no one has asked them to. hence, we check the list of drivers again, and see if some of the previously-unbound devices were erroneously bou

[dpdk-dev] [PATCH v3 0/2] Fix issues with VFIO

> -Original Message- > From: Burakov, Anatoly > Sent: Wednesday, June 18, 2014 8:07 AM > To: dev at dpdk.org > Cc: Richardson, Bruce; nhorman at tuxdriver.com > Subject: [PATCH v3 0/2] Fix issues with VFIO > > This patchset fixes an issue with VFIO where DPDK initialization could > fail ev

[dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

Thanks, Mark, the comment is really help. -Original Message- From: Gray, Mark D [mailto:mark.d.g...@intel.com] Sent: Wednesday, June 18, 2014 4:53 PM To: GongJinrong; 'Thomas Monjalon' Cc: dev at dpdk.org Subject: RE: [dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example? > > H

[dpdk-dev] [PATCH v5 6/6] Link Bonding Library doxygen additions

Signed-off-by: Declan Doherty --- doc/doxy-api-index.md |1 + doc/doxy-api.conf |1 + 2 files changed, 2 insertions(+), 0 deletions(-) diff --git a/doc/doxy-api-index.md b/doc/doxy-api-index.md index 7b26e98..ee3ad4f 100644 --- a/doc/doxy-api-index.md +++ b/doc/doxy-api-index.md @@

[dpdk-dev] [PATCH v5 5/6] testpmd link bonding additions

- Includes the ability to create new bonded devices. - Add /remove bonding slave devices. - Interogate bonded device stats/configuration - Change bonding modes and select balance transmit polices Signed-off-by: Declan Doherty --- app/test-pmd/cmdline.c| 579 +

[dpdk-dev] [PATCH v5 4/6] Link bonding Unit Tests

Including: - code to generate packet bursts for testing rx and tx functionality of bonded device - virtual/stubbed out ethdev for use as slave ethdev in testing Signed-off-by: Declan Doherty --- app/test/Makefile |4 +- app/test/commands.c |7 + app/tes

[dpdk-dev] [PATCH v5 3/6] EAL support for link bonding device initialization

Updating functionality in EAL to support adding link bonding devices via ?vdev option. Link bonding devices will be initialized after all physical devices have been probed and initialized. Signed-off-by: Declan Doherty --- lib/librte_eal/bsdapp/eal/eal.c | 10 - lib/librte_eal/

[dpdk-dev] [PATCH v5 2/6] Support for unique interface naming of pmds

Adding support to rte_eth_dev_data structure to support unique name identifier for ethdevs to support adding slave ethdevs (specifically virtual devices which have no public unique identifier) to a link bonding device. This changes the API rte_eth_dev_allocate() to require a const char *name when a

[dpdk-dev] [PATCH v5 1/6] Link Bonding Library (lib/librte_pmd_bond)

Initial release with support for Mode 0 - Round Robin Mode 1 - Active Backup Mode 2 - Balance -> Supports 3 transmit polices (layer 2, layer 2+3, layer 3+4) Mode 3 - Broadcast Signed-off-by: Declan Doherty --- config/common_bsdapp |5 + config/common_linuxapp |

[dpdk-dev] [PATCH v5 0/6] Link Bonding Library

This patch contains the initial release of the Link Bonding PMD Library Supporting bonding modes: 0 - Round Robin 1 - Active Backup 2 - Balance (Supporting 3 transmission polices) layer 2, layer 2+3, layer 3+4 3 - Broadcast Version 5 of patch set: Contains changes to EAL code to allow

[dpdk-dev] [dpdk-announce] release candidate 1.7.0-rc1

The first release candidate of version 1.7.0 can be downloaded here: http://dpdk.org/browse/dpdk/tag/?id=v1.7.0-rc1 Please test it. The release 1.7.0 should be ready by end of June if things go well. Some patches are pending for integration in next release candidate: - link bonding

[dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

Ok, thanks Thomas, I will try memnic. -Original Message- From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] Sent: Wednesday, June 18, 2014 4:20 PM To: GongJinrong Cc: dev at dpdk.org Subject: Re: [dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example? Hi, 2014-06-18 15:56,

[dpdk-dev] [PATCH 2/2] Patch to allow live migration of a VM with US-VHost.

Signed-off-by: Claire Murphy --- examples/vhost/vhost-net-cdev.c | 18 ++ examples/vhost/virtio-net.c |8 +++- 2 files changed, 25 insertions(+), 1 deletions(-) diff --git a/examples/vhost/vhost-net-cdev.c b/examples/vhost/vhost-net-cdev.c index ef42e88..e942df0 10

[dpdk-dev] [PATCH 1/2] Patch for Qemu wrapper for US-VHost to ensure Qemu process ends when VM is shutdown.

Signed-off-by: Claire Murphy --- examples/vhost/libvirt/qemu-wrap.py | 31 +++ 1 files changed, 27 insertions(+), 4 deletions(-) diff --git a/examples/vhost/libvirt/qemu-wrap.py b/examples/vhost/libvirt/qemu-wrap.py index e2d68a0..bfe668a 100755 --- a/examples/vho

[dpdk-dev] [PATCH 0/2] *** SUBJECT HERE ***

*** BLURB HERE *** Claire Murphy (2): Patch for Qemu wrapper for US-VHost to ensure Qemu process ends when VM is shutdown. Patch to allow live migration of a VM with US-VHost. examples/vhost/libvirt/qemu-wrap.py | 31 +++ examples/vhost/vhost-net-cdev.c

[dpdk-dev] vfio detection

> -Original Message- > From: Burakov, Anatoly > Sent: Wednesday, June 18, 2014 4:01 AM > To: Richardson, Bruce; dev at dpdk.org > Subject: RE: vfio detection > > Hi Bruce, > > > > > I have a number of NIC ports which were working correctly yesterday > > > > and are bound correctly to the

[dpdk-dev] [PATCH v3 2/2] vfio: more verbose error messages

also, making VFIO code distinguish between actual unexpected values and ioctl() failures, providing appropriate error messages. Signed-off-by: Anatoly Burakov --- lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 48 -- 1 file changed, 32 insertions(+), 16 deletions(-) di

[dpdk-dev] [PATCH v3 1/2] vfio: open VFIO container at startup rather than during init

Currently, VFIO only checks for being able to access the /dev/vfio directory when initializing VFIO, deferring actual VFIO container initialization to VFIO binding code. This doesn't bode well for when VFIO container cannot be initialized for whatever reason, because it results in unrecoverable err

[dpdk-dev] [PATCH v3 0/2] Fix issues with VFIO

This patchset fixes an issue with VFIO where DPDK initialization could fail even if the user didn't want to use VFIO in the first place. Also, more verbose and descriptive error messages were added to VFIO code, for example distinguishing between a failed ioctl() call and an unsupported VFIO API ve

[dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

Hi, I want find a zero copy framework from host to vm without any physical NIC device, it seems l2fwd-ivshmem can be used, but I have problems to run this example: 1. there is no document about this example, even a simple readme :-( 2. does this example need ovdk? 3. can I use standa

[dpdk-dev] [PATCH 10/10] rte_ip_frag: API header file fix

Signed-off-by: Anatoly Burakov --- lib/librte_ip_frag/rte_ip_frag.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/librte_ip_frag/rte_ip_frag.h b/lib/librte_ip_frag/rte_ip_frag.h index 84952a1..e0936dc 100644 --- a/lib/librte_ip_frag/rte_ip_frag.h +++ b/lib/librte_ip

[dpdk-dev] [PATCH 09/10] ip_reassembly: small fixes

Adding check for non-existent ports in portmask. Also, making everything NUMA-related depend on lcore sockets, not device sockets. This is because the init_mem() function allocates all data structures based on NUMA nodes of the lcores in the coremask. Therefore, when no cores are on socket 0, but

[dpdk-dev] [PATCH 08/10] ip_fragmentation: small fixes

Adding check for non-existent ports in portmask. Also, making everything NUMA-related depend on lcore sockets, not device sockets. This is because the init_mem() function allocates all data structures based on NUMA nodes of the lcores in the coremask. Therefore, when no cores are on socket 0, but

[dpdk-dev] [PATCH 07/10] ip_frag: fix order of arguments to key compare function

when using key compare function, it uses key length of the first argument to determine how long should be the keys that are compared. however, currently we are passing a key from the fragmentation table as first argument. the problem with this is that this key is potentially uninitialized (i.e. con

[dpdk-dev] [PATCH 06/10] ip_frag: replace memmove with custom copying

some implementations of memmove may make a copy of src before writing to dst. we avoid that by explicitly writing from src to dst backwards. Signed-off-by: Anatoly Burakov --- lib/librte_ip_frag/rte_ipv6_reassembly.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git

[dpdk-dev] [PATCH 05/10] ip_frag: small fix, replace hardcode with a macro

Signed-off-by: Anatoly Burakov --- lib/librte_ip_frag/ip_frag_internal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/librte_ip_frag/ip_frag_internal.c b/lib/librte_ip_frag/ip_frag_internal.c index 219221f..6203740 100644 --- a/lib/librte_ip_frag/ip_frag_internal.c ++

[dpdk-dev] [PATCH 04/10] ip_frag: fix stats macro, rename rte_ip_frag_tbl_stat structure

This also makes ip_reassembly sample application statistics to obey the CONFIG_RTE_LIBRTE_IP_FRAG_FRAG_TBL_STATS config option Signed-off-by: Anatoly Burakov --- config/common_bsdapp | 1 + config/common_linuxapp | 1 + examples/ip_reassembly/main.c| 4 ++-- lib/librte_

[dpdk-dev] [PATCH 03/10] ip_frag: renaming rte_ip_frag_pkt to ip_frag_pkt

Signed-off-by: Anatoly Burakov --- lib/librte_ip_frag/ip_frag_common.h | 18 +- lib/librte_ip_frag/ip_frag_internal.c| 20 ++-- lib/librte_ip_frag/rte_ip_frag.h | 12 ++-- lib/librte_ip_frag/rte_ipv4_reassembly.c | 4 ++-- lib/librte_ip_f

[dpdk-dev] [PATCH 02/10] ip_frag: fix debug macros

Signed-off-by: Anatoly Burakov --- lib/librte_ip_frag/rte_ipv4_reassembly.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/librte_ip_frag/rte_ipv4_reassembly.c b/lib/librte_ip_frag/rte_ipv4_reassembly.c index cbac413..c14c677 100644 --- a/lib/librte_ip_frag/rte_ip

[dpdk-dev] [PATCH 01/10] ip_frag: rename RTE_IP_FRAG_ASSERT to IP_FRAG_ASSERT

Signed-off-by: Anatoly Burakov --- lib/librte_ip_frag/ip_frag_common.h | 4 ++-- lib/librte_ip_frag/rte_ipv4_fragmentation.c | 2 +- lib/librte_ip_frag/rte_ipv6_fragmentation.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/librte_ip_frag/ip_frag_common.h b/l

[dpdk-dev] [PATCH 00/10] rte_ip_frag: various fixes for lib and examples

This patchset fixes a few issues found during validation, and also does a bunch of renames (so that internally-used data structures aren't starting with rte_) and fixes a few typos. Anatoly Burakov (10): ip_frag: rename RTE_IP_FRAG_ASSERT to IP_FRAG_ASSERT ip_frag: fix debug macros ip_frag:

[dpdk-dev] [PATCH v3 0/2] Fix issues with VFIO

On Wed, Jun 18, 2014 at 04:07:15PM +0100, Anatoly Burakov wrote: > This patchset fixes an issue with VFIO where DPDK initialization could > fail even if the user didn't want to use VFIO in the first place. Also, > more verbose and descriptive error messages were added to VFIO code, for > example di

[dpdk-dev] [PATCH v3 0/9] Make DPDK tailqs fully local

> This issue was reported by OVS-DPDK project, and the fix should go to > upstream DPDK. This is not memnic-related - this is to do with > DPDK's rte_ivshmem library. > > Every DPDK data structure has a corresponding TAILQ reserved for it in > the runtime config file. Those TAILQs are fully loca

[dpdk-dev] [PATCH v2 2/2] vfio: more verbose error messages

Signed-off-by: Anatoly Burakov CC: Neil Horman --- lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 48 -- 1 file changed, 32 insertions(+), 16 deletions(-) diff --git a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c index 9eb5d

[dpdk-dev] [PATCH v2 1/2] vfio: open VFIO container at startup rather than during init

Currently, VFIO only checks for being able to access the /dev/vfio directory when initializing VFIO, deferring actual VFIO container initialization to VFIO binding code. This doesn't bode well for when VFIO container cannot be initialized for whatever reason, because it results in unrecoverable err

[dpdk-dev] [PATCH v2 0/2] Fix issues with VFIO

This patchset fixes an issue with VFIO where DPDK initialization could fail even if the user didn't want to use VFIO in the first place. Also, more verbose and descriptive error messages were added to VFIO code, for example distinguishing between a failed ioctl() call and an unsupported VFIO API ve

[dpdk-dev] Testing memnic for VM to VM transfer

2014-06-18 11:42, Hiroshi Shimamoto: > 2014-06-18 19:26, GongJinrong: > > Do you have any idea that how to write a host application > > to put the data to guest memnic PMD? > > Yes, basically I made the MEMNIC interface work with DPDK vSwitch. > > By the way, you can mmap() the shm which specifie

[dpdk-dev] [PATCH v3 9/9] rte_acl: make acl tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_acl/acl.h | 1 - lib/librte_acl/rte_acl.c | 74 +++- 2 files changed, 60 insertions(+), 15 deletions(-) diff --git a/lib/librte_acl/acl.h b/lib/librte_acl/acl.h index e6d7985..b9d63fd 100644 --- a/lib

[dpdk-dev] [PATCH v3 8/9] rte_lpm6: make lpm6 tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_lpm/rte_lpm6.c | 62 ++- 1 file changed, 51 insertions(+), 11 deletions(-) diff --git a/lib/librte_lpm/rte_lpm6.c b/lib/librte_lpm/rte_lpm6.c index 56c74a1..73b48d0 100644 --- a/lib/librte_lpm/rte_lpm6.c +

[dpdk-dev] [PATCH v3 7/9] rte_lpm: make lpm tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_lpm/rte_lpm.c | 65 lib/librte_lpm/rte_lpm.h | 2 -- 2 files changed, 54 insertions(+), 13 deletions(-) diff --git a/lib/librte_lpm/rte_lpm.c b/lib/librte_lpm/rte_lpm.c index 592750e..6a49d43 100644

[dpdk-dev] [PATCH v3 6/9] rte_mempool: make mempool tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_mempool/Makefile | 3 ++- lib/librte_mempool/rte_mempool.c | 37 - lib/librte_mempool/rte_mempool.h | 2 -- 3 files changed, 30 insertions(+), 12 deletions(-) diff --git a/lib/librte_mempool/Makefile b/lib/

[dpdk-dev] [PATCH v3 5/9] rte_fbk_hash: make rte_fbk_hash tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_hash/rte_fbk_hash.c | 73 ++ lib/librte_hash/rte_fbk_hash.h | 3 -- 2 files changed, 59 insertions(+), 17 deletions(-) diff --git a/lib/librte_hash/rte_fbk_hash.c b/lib/librte_hash/rte_fbk_hash.c index 4d6755

[dpdk-dev] [PATCH v3 4/9] rte_hash: make rte_hash tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_hash/rte_hash.c | 61 +++--- lib/librte_hash/rte_hash.h | 2 -- 2 files changed, 52 insertions(+), 11 deletions(-) diff --git a/lib/librte_hash/rte_hash.c b/lib/librte_hash/rte_hash.c index d4221a8..eea5c01 1

[dpdk-dev] [PATCH v3 3/9] rte_ring: make ring tailq fully local

Signed-off-by: Anatoly Burakov --- lib/librte_eal/linuxapp/eal/eal_ivshmem.c | 17 ++-- lib/librte_ring/Makefile | 4 ++-- lib/librte_ring/rte_ring.c| 33 +++ lib/librte_ring/rte_ring.h| 2 -- 4 files chan

[dpdk-dev] [PATCH v3 2/9] rte_tailq: change rte_dummy to rte_tailq_entry, add data pointer

Signed-off-by: Anatoly Burakov --- app/test/test_tailq.c | 33 --- lib/librte_eal/common/eal_common_tailqs.c | 2 +- lib/librte_eal/common/include/rte_tailq.h | 9 + 3 files changed, 23 insertions(+), 21 deletions(-) diff --git a/app/tes

[dpdk-dev] [PATCH v3 1/9] eal: map shared config into exact same address as primary process

Shared config is shared across primary and secondary processes. However,when using rte_malloc, the malloc elements keep references to the heap inside themselves. This heap reference might not be referencing a local heap because the heap reference points to the heap of whatever process has allocated

[dpdk-dev] [PATCH v3 0/9] Make DPDK tailqs fully local

This issue was reported by OVS-DPDK project, and the fix should go to upstream DPDK. This is not memnic-related - this is to do with DPDK's rte_ivshmem library. Every DPDK data structure has a corresponding TAILQ reserved for it in the runtime config file. Those TAILQs are fully local to the proce

[dpdk-dev] [PATCH v5 0/6] Link Bonding Library

On Wed, Jun 18, 2014 at 05:14:17PM +0100, Declan Doherty wrote: > This patch contains the initial release of the Link Bonding PMD Library > > Supporting bonding modes: > 0 - Round Robin > 1 - Active Backup > 2 - Balance (Supporting 3 transmission polices) > layer 2, layer 2+3, layer 3+4 >

[dpdk-dev] [PATCH v3] cpu_layout.py: adjust output format to align

Bug: when "core id" is greater than 9, the cpu_layout.py output doesn't align. Socket 0Socket 1 - - Core 9 [4, 16] [10, 22] Core 10 [5, 17] [11, 23] Solution: adjust output format to align based on the maximum length of the

[dpdk-dev] Testing memnic for VM to VM transfer

Hi, > Subject: Re: [dpdk-dev] Testing memnic for VM to VM transfer > > 2014-06-18 11:42, Hiroshi Shimamoto: > > 2014-06-18 19:26, GongJinrong: > > > Do you have any idea that how to write a host application > > > to put the data to guest memnic PMD? > > > > Yes, basically I made the MEMNIC interf

[dpdk-dev] Testing memnic for VM to VM transfer

Hi, > Subject: ##freemail## RE: ##freemail## RE: [dpdk-dev] Testing memnic for VM > to VM transfer > > Hi, Hiroshi > >Do you mean I must use DPDK vSwitch in host when I use MEMNIC PMD in > guest VM? actually, I just want a channel which can put the data from host > to guest quickly. Do you

[dpdk-dev] [PATCH v2 00/27] Add i40e PMD support

2014-06-18 08:51, Zhang, Helin: > Thomas Monjalon: > > Some things could be cleaned up later, especially i40e specific flags in > > generic API must be removed. Please work on a patch for next release. > > Btw, what do you mean the i40e specific flags in generic API? Did you mean > the new flags d

[dpdk-dev] ##freemail## RE: Testing memnic for VM to VM transfer

Hi, > Subject: ##freemail## RE: [dpdk-dev] Testing memnic for VM to VM transfer > > Hi, Hiroshi > >I just start to learn DPDK and memnic, in memnic guide, you said "On > host, the shared memory must be initialized by an application using memnic", > I am not so clear that how to initialize th

[dpdk-dev] [PATCH] vfio: open VFIO container at startup rather than during init

Hi Neil > I think what Thomas wants is for you to resend the patch with a proper > changelog entry added to it, so the commit has an explination of what was > changed and, for posterity. Got it. Can I also incorporate your changes to error codes as well? Best regards, Anatoly Burakov DPDK SW Eng

[dpdk-dev] vfio detection

Hi Bruce, > > > I have a number of NIC ports which were working correctly yesterday > > > and are bound correctly to the igb_uio driver - and I want to keep > > > using them through the igb_uio driver for now, not vfio. However, > > > whenever I run a dpdk application today, I find that the vfio k

[dpdk-dev] [memnic PATCH v2 5/5] linux: support MTU change

From: Hiroshi Shimamoto Add the capability to change MTU. On MTU change, remember the corresponding frame size and request new frame size to the host on reset, if the host MEMNIC has that feature. Don't trust framesz of header in general usage, because host might change the value unexpectedly.

[dpdk-dev] [PATCH] vfio: open VFIO container at startup rather than during init

Hi Cristian, > I would suggest we add a log message explaining which mechanism is loaded > (igb_uio/vfio) and why (e.g. tried vfio first but container could not be > opened, so falling back to igb_uio, etc). This already happens. If the container could not be loaded for whatever reason, the log

[dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

Hi, 2014-06-18 15:56, GongJinrong: >I want find a zero copy framework from host to vm without any physical > NIC device, I think memnic is what you want: http://dpdk.org/doc/memnic-pmd > it seems l2fwd-ivshmem can be used, but I have problems to run > this example: >1. there is n

[dpdk-dev] [PATCH] vfio: open VFIO container at startup rather than during init

Hi Anatoly, I would suggest we add a log message explaining which mechanism is loaded (igb_uio/vfio) and why (e.g. tried vfio first but container could not be opened, so falling back to igb_uio, etc). Regards, Cristian -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behal

[dpdk-dev] [PATCH v2 0/2] Fix issues with VFIO

On Wed, Jun 18, 2014 at 02:07:17PM +0100, Anatoly Burakov wrote: > This patchset fixes an issue with VFIO where DPDK initialization could > fail even if the user didn't want to use VFIO in the first place. Also, > more verbose and descriptive error messages were added to VFIO code, for > example di

[dpdk-dev] [PATCH 1/9] eal: map shared config into exact same address as primary process

Hi Konstantin, > I think we introduce a race window here. > If secondary process would do first mmap() before rte_config.mem_config- > >mem_cfg_addr was properly set by primary process, then it will try to do > second mmap() with wrong address. > I think we need to do second mmap() straight after

[dpdk-dev] [PATCH] vfio: open VFIO container at startup rather than during init

Hi Thomas, > Subject: Re: [dpdk-dev] [PATCH] vfio: open VFIO container at startup rather > than during init > > > Signed-off-by: Anatoly Burakov > > Please Anatoly, could you provide a text explaining what was broken and > why you fixed it this way? What was broken was if, for some reason, VFI

[dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

> > Hi, > > 2014-06-18 15:56, GongJinrong: > >I want find a zero copy framework from host to vm without any > > physical NIC device, > > I think memnic is what you want: > http://dpdk.org/doc/memnic-pmd > > > it seems l2fwd-ivshmem can be used, but I have problems to run this > > exam

[dpdk-dev] [PATCH v2 00/27] Add i40e PMD support

-Original Message- From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] Sent: Wednesday, June 18, 2014 12:28 AM To: Zhang, Helin; Chen, Jing D Cc: dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 00/27] Add i40e PMD support > The 2nd version of series of patches are to add i40e PMD

[dpdk-dev] [PATCH] vfio: open VFIO container at startup rather than during init

On Wed, Jun 18, 2014 at 11:02:23AM +, Burakov, Anatoly wrote: > Hi Neil > > > I think what Thomas wants is for you to resend the patch with a proper > > changelog entry added to it, so the commit has an explination of what was > > changed and, for posterity. > > Got it. Can I also incorporate

[dpdk-dev] [PATCH] vfio: open VFIO container at startup rather than during init

On Wed, Jun 18, 2014 at 10:26:08AM +, Burakov, Anatoly wrote: > Hi Cristian, > > > I would suggest we add a log message explaining which mechanism is loaded > > (igb_uio/vfio) and why (e.g. tried vfio first but container could not be > > opened, so falling back to igb_uio, etc). > > This alre

[dpdk-dev] Testing memnic for VM to VM transfer

Hi, > Subject: [dpdk-dev] Testing memnic for VM to VM transfer > > Hi everyone: > We are interested in testing the performance of the memnic driver > posted at http://dpdk.org/browse/memnic/refs/. > We want to compare its performance compared to other techniques to transfer > packet

[dpdk-dev] [PATCH v3 0/7] add mtu and flow control handlers

2014-06-17 22:30, Ananyev, Konstantin: > > This patchset introduces 3 new ethdev operations: flow control parameters > > retrieval and mtu get/set operations. > > > > David Marchand (3): > > ethdev: add autoneg parameter in flow ctrl accessors > > ethdev: store min rx buffer size > > ethdev: