On 2015/8/7 13:37, Zhang, Helin wrote:
>
>> -Original Message-
>> From: Qiu, Michael
>> Sent: Friday, August 7, 2015 11:53 AM
>> To: Zhang, Helin; dev at dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH] testpmd: modify the mac of csum forwarding
>>
>> On 2015/8/7 9:06, Zhang, Helin wrote:
-
> -Original Message-
> From: Qiu, Michael
> Sent: Friday, August 7, 2015 11:53 AM
> To: Zhang, Helin; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] testpmd: modify the mac of csum forwarding
>
> On 2015/8/7 9:06, Zhang, Helin wrote:
> >
> >> -Original Message-
> >> From: dev
Hi again,
two findings in the vhost-switch example code that can cause grey hair
for starters:
- MAX_QUEUES of 512 causes pretty high memory need for the application
(something between 1 and 2G) - is that really needed? I'm now running
with 32, and I'm able to get away with 256M. Can we tune
On VHOST_*_RESET_OWNER, we reinitialize the device but without telling
the application. That will cause crashes when it continues to invoke
vhost services on the device. Fix it by calling the destruction hook if
the device is still in use.
Signed-off-by: Jan Kiszka
---
This is the surprisingly s
On 2015/8/7 9:06, Zhang, Helin wrote:
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michael Qiu
>> Sent: Thursday, August 6, 2015 8:29 PM
>> To: dev at dpdk.org
>> Subject: [dpdk-dev] [PATCH] testpmd: modify the mac of csum forwarding
>>
>> For some ethn
On 2015/8/7 9:05, De Lara Guarch, Pablo wrote:
> Hi Michael,
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michael Qiu
>> Sent: Friday, August 07, 2015 4:29 AM
>> To: dev at dpdk.org
>> Subject: [dpdk-dev] [PATCH] testpmd: modify the mac of csum forwardi
To obtain detachable flag, pci_drv is accessed in rte_eth_dev_is_detachable().
But pci_drv is only valid if port is enabled. Not to cause illegal access,
add rte_eth_dev_is_valid_port() before accessing.
Signed-off-by: Tetsuya Mukawa
---
lib/librte_ether/rte_ethdev.c | 2 +-
1 file changed, 1 in
There is no sync between host and guest to allow removal of memzones,
and freeing them result in undefined behavior.
In the guest, we identify IVSHMEM memsegs/memzones by having
ioremap_addr != 0. In the host, nothing is done to the memzone, meaning
ioremap_addr == 0.
As a solution, mark memzones
After the changes introduced by Dynamic Memzones, all the memsegs were
added to the malloc heap during init.
Those changes did not account for IVSHMEM memsegs which should not be
added to the malloc heap as part of available memory.
Fixes: fafcc11985a2 ("mem: rework memzone to be allocated by mal
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michael Qiu
> Sent: Thursday, August 6, 2015 8:29 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] testpmd: modify the mac of csum forwarding
>
> For some ethnet-switch like intel RRC, all the packet for
Hi Michael,
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michael Qiu
> Sent: Friday, August 07, 2015 4:29 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] testpmd: modify the mac of csum forwarding
>
> For some ethnet-switch like intel RRC, all the
Hi,
I was wondering if I'm alone with this: the vhost-switch example crashes
on client disconnects if the client send a RESET_OWNER message. That's
at least the case for QEMU and vhost-user mode (I suppose vhost-cuse is
legacy now). And it really ruins the party when playing with this
because ever
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Cristian Dumitrescu
> Sent: Thursday, August 6, 2015 2:48 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: ip_pipeline app user guide
>
> Added more extensive documentation for ip_pipeline application
Hi Harpal,
> I think maintaining a ref count of groups will solve this problem.
Yes, refcounting seems like the best way to solve this problem.
> Additionally, I have found a bug in existing design in case of multiple
> devices of same group.
> <...>
> Therefore, I will provide a fix?for this
Changes include moving common functions in eal_thread.c in
linuxapp and bsdapp into common/eal_common_thread.c file.
Compiled on Linux for following targets
> x86_64-native-linuxapp-gcc
> x86_64-native-linuxapp-clang
> x86_x32-native-linuxapp-gcc
Compiled on FreeBSD for following targets
As per Thomas's suggestion we will split remaining files in EAL cleanup
effort into multiple patches, eal_thread.c is first in this series.
Ravi Kerur (1):
Move EAL thread common functions
lib/librte_eal/bsdapp/eal/Makefile| 3 +-
lib/librte_eal/bsdapp/eal/eal_thread.c| 152 -
Hi Tetsuya,
On Thu, Aug 6, 2015 at 7:25 PM, Tetsuya Mukawa wrote:
> On 2015/08/07 3:04, Ravi Kerur wrote:
> > diff --git a/drivers/net/enic/enic_ethdev.c
> b/drivers/net/enic/enic_ethdev.c
> > index 8280cea..472ef5a 100644
> > --- a/drivers/net/enic/enic_ethdev.c
> > +++ b/drivers/net/enic/enic_
Test failed on verification if number of bytes
transmitted on each slave is not less than 90%
and greater than 110% of mean value of bytes transmitted
thru one slave. This was verified on a real system
but is difficult to achieve using virtualpmd.
That's why for unit tests only, it is sufficient to
On slave activation in LACP (8023AD) SOCKET_ANY_ID (which is -1)
is being casted to unsigned char and then to signed int.
The result is that socket_id has value of 255, not -1.
This results to memory allocation failure.
Signed-off-by: Sergey Balabanov
---
drivers/net/bonding/rte_eth_bond_8023ad.
For some ethnet-switch like intel RRC, all the packet forwarded
out by DPDK will be dropped in switch side, so the packet
generator will never receive the packet.
Signed-off-by: Michael Qiu
---
app/test-pmd/csumonly.c | 4
1 file changed, 4 insertions(+)
diff --git a/app/test-pmd/csumonly.
On 2015/08/07 3:04, Ravi Kerur wrote:
> diff --git a/drivers/net/enic/enic_ethdev.c b/drivers/net/enic/enic_ethdev.c
> index 8280cea..472ef5a 100644
> --- a/drivers/net/enic/enic_ethdev.c
> +++ b/drivers/net/enic/enic_ethdev.c
> @@ -36,8 +36,8 @@
> #include
> #include
>
> -#include
> #inclu
On 07/08/2015 10:08, Pablo de Lara wrote:
> L3fwd was trying to use an inexistent function "simple_ipv6_fwd_4pkts",
> instead it should be "simple_ipv6_fwd_8pkts".
>
> Fixes: 80fcb4d4 ("examples/l3fwd: increase lookup burst size to 8")
>
> Signed-off-by: Pablo de Lara
> ---
>
Acked-by: Sergio Gonz
On 06/08/2015 12:07, Pablo de Lara wrote:
> Pablo de Lara (2):
>examples/vm_power_mgr: show warning when using systems with more than
> 64 cores
>doc: add known issue regarding VM power mgr in release notes
>
> doc/guides/rel_notes/known_issues.rst | 24
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Tetsuya Mukawa
> Sent: Friday, August 7, 2015 10:21 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] ethdev: Fix illegal access of
> rte_eth_dev_is_detachable()
>
> To obtain detachable flag, pci_drv is ac
L3fwd was trying to use an inexistent function "simple_ipv6_fwd_4pkts",
instead it should be "simple_ipv6_fwd_8pkts".
Fixes: 80fcb4d4 ("examples/l3fwd: increase lookup burst size to 8")
Signed-off-by: Pablo de Lara
---
examples/l3fwd/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi All,
I have an extremely simple test - I have just one single DPDK EAL
thread which pulls packets from one 10G port and just puts the packet
exactly as is (no changes) on another 10G port - I get 9.5million pps,
so far so good. So its like this
dpdk_rx
dpdk_tx
9.5 Millionpps
Now I do the bel
> -Original Message-
> From: Sergey Balabanov [mailto:balabanovsv at ecotelecom.ru]
> Sent: Friday, August 07, 2015 10:33 AM
> To: dev at dpdk.org
> Cc: De Lara Guarch, Pablo; Sergey Balabanov
> Subject: [PATCH v2] bonding: 8023ad: fix incorrect typecast of socket
>
> On slave activation
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Sergey Balabanov
> Sent: Wednesday, August 05, 2015 2:49 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] bonding: 8023ad: fix incorrect typecast of
> socket
>
> On slave activation in LACP (8023AD) SOCK
Tested-by: Marvin Liu
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara
> Sent: Thursday, August 06, 2015 7:08 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH 0/2] Warn user if system has more than 64 cores
> when using VM power manager
>
> -Original Message-
> From: Liang, Cunming
> Sent: Thursday, August 06, 2015 10:19 AM
> To: dev at dpdk.org
> Cc: Mcnamara, John; david.marchand at 6wind.com; Liang, Cunming
> Subject: [PATCH v1] doc: prog_guide update for RX interrupt event
>
> The patch updates the env_abstraction_laye
30 matches
Mail list logo
