On 08/14/2014 05:44 PM, Qiaobing Xie wrote:
> Hi,
>
> I got the following error when I tried to compile 1.7.0 release
> tarball on a Linux box (Ubuntu 12.04/kernel=3.13.0-32-generic,
> gcc=4.6.3):
>
>
> In file included from
> /home/qxie/dpdk-1.7.0/lib/librte_eal/linuxapp/kni/ethto
On 08/14/2014 05:55 PM, Wiles, Roger Keith wrote:
> For the SKB function change I had to change the ifdef in the kcompat.h file
> around line 3848 (I think) to:
>
> /* Changed the next line to use (3,13,8) instead of (3,14,0) KeithW */
> #if ( LINUX_VERSION_CODE < KERNEL_VERSION(3,13,8) )
>
On Jan 13, 2017 9:42 AM, "Jianfeng Tan" wrote:
Signed-off-by: Jianfeng Tan
---
.../img/virtio_user_as_excpetional_path.png| Bin 0 -> 38600 bytes
doc/guides/prog_guide/index.rst| 1 +
.../prog_guide/virtio_user_as_exceptional_path.rst | 104
+
3
On Wed, Dec 7, 2016 at 2:38 PM, Keith Wiles wrote:
>
> Signed-off-by: Keith Wiles
Tested-by: Aws Ismail
Hi everyone,
I am looking at this portion of the code in the app_thread.c file of the
QoS scheduler example application:
/*
* QoS parameters are encoded as follows:
* Outer VLAN ID defines subport
* Inner VLAN ID defines pipe
* Destination IP 0.0.XXX.0 defines traffic class
* Destination IP host
t and correct.
>
> Regards,
> Cristian
>
>
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Aws Ismail
> Sent: Saturday, February 14, 2015 7:35 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] Explanation of the QoS offset values used
Hi DPDKers,
I have a strange case where the Distributor example application is not
working when I use Intel's I35x (I354 specifically) 1Gig ports. The
app initializes fine but the port always comes with link down:
[root at localhost dpdk]# ./tools/dpdk_nic_bind.py -b igb_uio eth1 eth2
[root at
Hi Bruce,
As far as I have checked, testpmd and l2fwd apps work fine.
Aws\
On Mon, Jun 29, 2015 at 5:19 AM, Bruce Richardson
wrote:
> On Fri, Jun 26, 2015 at 03:37:08PM -0400, Aws Ismail wrote:
>> Hi DPDKers,
>>
>> I have a strange case where the Distributor examp
I am wondering if there is support for such device in the ixgbe PMD.
the dpdk nic bind script seems to see them correctly but when running
testpmd with those ports, they always come with link status down.
>From the dpdk_nic_bind script (snip):
Network devices using DPDK-compatible driver
===
Hi all,
I have sent in an earlier email, but it seems it did not get any reply.
I just wanted to confirm whether the 0x15ad X552/X557-AT 10GBase-T
devices are currently "fully" supported by DPDK (master).
Does anyone know about this?
I have looked at the ixgbe PMD code and I can see 0x15AD bein
On Fri, Nov 13, 2015 at 11:40 AM, Thomas Monjalon
wrote:
> 2015-11-13 11:32, Aws Ismail:
>> I just wanted to confirm whether the 0x15ad X552/X557-AT 10GBase-T
>> devices are currently "fully" supported by DPDK (master).
>
> My understanding is that it is suppo
The dpdk nic bind script seems to see them correctly but when running
testpmd with those ports, they always come with link status down.
>From the dpdk_nic_bind script (snip):
Network devices using DPDK-compatible driver
:03:00.0 'Ethernet Connectio
Hi Stephen, Ferruh,
As an end-user take on this (hence community comment) :), this ties into
the rte_eth_tap that Keith sent out and it has been acked and reviewed, So
I am trying to see the pros/cons of using this (kni pmd) vs. the tun/tap
PMD [1].
Previously, we were using Ferruh's KDP/KCP patc
Keith,
This won't build when integrated with v16.11. The register macro
prefix has been renamed. a v10 is needed.
diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
index 7f303db..297d4b6 100644
--- a/drivers/net/tap/rte_eth_tap.c
+++ b/drivers/net/tap/rte_eth_tap.c
@@ -75
(rte_eal_init+0xe09) [0x7f3e68ceaea9]]
2: [/usr/lib/librte_eal.so.3.1(__rte_panic+0xc0) [0x7f3e68ce9b5a]]
1: [/usr/lib/librte_eal.so.3.1(rte_dump_stack+0x18) [0x7f3e68cf2078]]
Aborted (core dumped)
root@
?localhost?
:~#
On Fri, Nov 25, 2016 at 2:38 PM, Aws Ismail wrote:
> Keith,
>
> T
15 matches
Mail list logo
