Hi Declan,
On Sun, Jun 29, 2014 at 1:49 PM, Declan Doherty
wrote:
> 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
> -
Hey Folks,
In my application, I'm seeing some design considerations in a project I'm
working on that push me towards the use of smaller memory page sizes. I'm
curious - is it possible in practical terms to run DPDK without hugepages?
If so, does anybody have any practical experience (or a
back-o
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Alex Markuze
> Sent: Monday, June 30, 2014 3:01 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] Memory Pinning.
>
> Hi, Guys.
> I have several newbie questions about the DPDK design I was hoping some one
> could
> -Original Message-
> From: Olivier MATZ [mailto:olivier.matz at 6wind.com]
> Sent: Monday, June 30, 2014 12:42 AM
> To: Richardson, Bruce; De Lara Guarch, Pablo; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] string: fix potential seg fault on snprintf
>
> Hello Bruce,
>
> On 06/27/2
Hi Matt,
On Mon, Jun 30, 2014 at 05:43:39PM -0500, Matt Laswell wrote:
> Hey Folks,
>
> In my application, I'm seeing some design considerations in a project I'm
> working on that push me towards the use of smaller memory page sizes. I'm
> curious - is it possible in practical terms to run DPDK
From: Pablo de Lara
In whitelist test, within EAL flags unit test, vdev flag
was being tested, but test fails, as a secondary process
cannot allocate memzones, so it cannot create the device
and application exits. Also, this can be tested in ring
pmd test, which needs vdev and not in whitelist, w
Hello Pablo,
On 06/30/2014 12:52 PM, Pablo de Lara wrote:
> From: Pablo de Lara
>
> Cmdline unit test calls several functions that use snprintf,
> with NULL pointer as the destination buffer. This patch
> eliminates these NULL pointer tests.
>
> Signed-off-by: Pablo de Lara
Acked-by: Olivier Ma
Hi, Guys.
I have several newbie questions about the DPDK design I was hoping some one
could answer.
Both in the RX and TX flow, the Buffer Memory must be pinned and not
swappable.
In RDMA, memory is explicitly registered and made pinned (to the limit
defined @ /etc/security/limits.conf) .With regu
From: Pablo de Lara
Cmdline unit test calls several functions that use snprintf,
with NULL pointer as the destination buffer. This patch
eliminates these NULL pointer tests.
Signed-off-by: Pablo de Lara
---
app/test/test_cmdline_etheraddr.c |7 ---
app/test/test_cmdline_num.c |
Hi Declan,
2014-06-29 18:49, Declan Doherty:
> This patchset contains the name change fix in the link bonding library
> makefile. I have also put a change into the unit test application makefile
> so that the link bonding tests are not built if the library is also not
> being built. It doesn't mak
Hi Declan,
2014-06-29 18:49, Declan Doherty:
> --- a/mk/rte.app.mk
> +++ b/mk/rte.app.mk
> @@ -205,6 +205,10 @@ ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
> LDLIBS += -lrte_pmd_pcap -lpcap
> endif
>
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_BOND),y)
> +LDLIBS += -lrte_pmd_bond
> +endif
> +
> endif
This p
Hi Declan,
2014-06-29 18:49, Declan Doherty:
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_BOND),y)
> +SRCS-$(CONFIG_RTE_APP_TEST) += virtual_pmd.c
> +SRCS-$(CONFIG_RTE_APP_TEST) += packet_burst_generator.c
> +SRCS-$(CONFIG_RTE_APP_TEST) += test_link_bonding.c
> +endif
> ifeq ($(CONFIG_RTE_APP_TEST),y)
> SRC
Hi,
2014-06-30 08:36, Cao, Waterman:
> We tested this patch with latest RHEL 7. (3.10.0-123) on RC2.
> It fixed compilation error in KNI.
> Please merge this patch in the RC3.
> Although We don't meet this compilation in RHEL 7 beta version, but Hiroshi
> caught it in latest version.
> It seem
Signed-off-by: Maciej Gajdzica
---
lib/librte_eal/common/include/rte_pci_dev_ids.h | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/lib/librte_eal/common/include/rte_pci_dev_ids.h
b/lib/librte_eal/common/include/rte_pci_dev_ids.h
index 9c1ee04..b0737a5 100644
--- a/li
Signed-off-by: Maciej Gajdzica
---
lib/librte_eal/bsdapp/nic_uio/nic_uio.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
b/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
index 3fe6f1c..00c9a8d 100644
--- a/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
+++ b/lib/l
Signed-off-by: Maciej Gajdzica
---
config/common_bsdapp | 10 ++
1 file changed, 10 insertions(+)
diff --git a/config/common_bsdapp b/config/common_bsdapp
index 578d510..87edada 100644
--- a/config/common_bsdapp
+++ b/config/common_bsdapp
@@ -177,6 +177,16 @@ CONFIG_RTE_LIBRTE_VIRTIO_DEB
From: Maciej Gajdzica
Signed-off-by: Maciej Gajdzica
---
lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c
b/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c
index cb711dc..69e01c1 100644
--- a/lib/librte_pmd_vmxnet3/vmxnet3_rx
Enabled VMXNET3 compilation for FreeBSD in the makefiles. Fixed some
minor issues to make it run.
Maciej Gajdzica (4):
vmxnet3: Removed unused include that broke VMXNET3 driver compilation
under FreeBSD.
vmxnet3: Added makefile entries to compile VMXNET3 driver under
FreeBSD.
vmxnet3
> > -Original Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Friday, June 27, 2014 10:47 AM
> > To: dev at dpdk.org
> > Subject: [dpdk-dev] [PATCH] app/test: fix build switches to enable cmdline
> > tests
> >
> > There were 2 typos since these
Hello Bruce,
On 06/27/2014 06:36 PM, Richardson, Bruce wrote:
> Famous last words include "that could never happen!" :-)
> Since this is not a performance critical piece of code, it does not hurt to
> leave the Null-check in, and get the additional safety of checking for
> invalid inputs.
The "
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Monday, June 30, 2014 10:21 AM
> To: Doherty, Declan
> Cc: dev at dpdk.org
> Subject: Re: [PATCH v11 0/5] link bonding library
>
> Hi Declan,
>
> 2014-06-29 18:49, Declan Doherty:
> > This patchset
Hi Thomas,
We tested this patch with latest RHEL 7. (3.10.0-123) on RC2.
It fixed compilation error in KNI.
Please merge this patch in the RC3.
Although We don't meet this compilation in RHEL 7 beta version, but Hiroshi
caught it in latest version.
It seems that there are a difference betwee
Hi Hiroshi,
We found that there is a little difference between your environment and ours.
Our Env:
Linux RHEL-7.0-64 3.10.0-54.0.1.el7.x86_64 #1 SMP Tue Nov 26 16:51:22 EST 2013
x86_64 x86_64 x86_64 GNU/Linux gcc : gcc version 4.8.2 20131106 (Red Hat
4.8.2-3) (GCC)
Your Env:
Linux RHEL7-1 3.10.0
Hi,
> Subject: Re: [dpdk-dev] [PATCH] kni: compatibility with RHEL 7
>
> Hi,
>
> > Subject: RE: [dpdk-dev] [PATCH] kni: compatibility with RHEL 7
> >
> > Hi Hiroshi,
> >
> > Helin submitted one patch to fix compilation error in the redhat 6.4 and
> > 6.5.
> > Patch title is [dpdk-dev] [PATC
> This patchset provides variable frame size functionality with MEMNIC
> extra features framework.
>
> First, update the memnic.h to synchronise upstream data structure which
> has extra feature framework.
> Next, prepare for changing frame size.
> Finally implement frame size negotiation with hos
> Calling netif_receive_skb() from memnic thread may cause deadlock, if
> softirq is not disabled.
>
> The netif_receive_skb() should be called in softirq context, but memnic
> thread is not softirq context. That may conflict softirq work like a
> timer handler in kernel network stack.
>
> Signed
26 matches
Mail list logo
