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
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
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
+++
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
---
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
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
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
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
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
> -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
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
@@
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 +
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
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
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
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
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
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
---
*** 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
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(-)
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
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
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
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
+++
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
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.
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 ++--
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
---
> 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
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
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
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
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
---
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
>
> 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
> >
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
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
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
>
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
> >
59 matches
Mail list logo