[dpdk-dev] are these bypass api supported on Intel Bandon Beach card : of device id : 8086:155d

* int rte_eth_dev_bypass_wd_timeout_show (uint8_t port, thanks Sharath

[dpdk-dev] are these bypass api supported on Intel Bandon Beach card : of device id : 8086:155d

can anyone please let me know about this... thanks, Sharath On Sat, Mar 1, 2014 at 5:06 PM, Sharath wrote: > Hi > > we are using DPDK 1.5.1_7. > our PCI slot has Intel Bandon Beach NIC. > > > Can anyone please let me know, whether the below api's are supported in

[dpdk-dev] are these bypass api supported on Intel Bandon Beach card : of device id : 8086:155d

the NIC into norm state using the same set of API, the NIC is not coming to norm state. the link state is showing as down. Is there any restriction/any other setting required to work with these api;s/ thanks, Sharath On Mon, Mar 3, 2014 at 3:54 PM, Ananyev, Konstantin < konstantin.ananyev

[dpdk-dev] bypass event for reboot

s. thanks in advance Sharath.

[dpdk-dev] bypass event for reboot

Hi Konstantin, could you please comment on this. thanks, Sharath On Fri, Apr 4, 2014 at 6:12 PM, Sharath wrote: > Hi! > > I have been able to use the below API to set the bypass event on power off > and power on > > * int rte_eth_dev_bypass_event_store (uint8_t po

[dpdk-dev] checking packet drop at NIC

hi Vladimir, I would like to know if there are any callback mechanism to detect FIFO errors in NIC ? could you please let me know. Tx -SB On Fri, Jan 31, 2014 at 12:56 PM, Sharath wrote: > thank you Vladimir. > > > On Fri, Jan 31, 2014 at 12:36 PM, Vladimir Medvedkin > wrote:

[dpdk-dev] checking packet drop at NIC

hi all, can anyone please let me know about this ?? Tx, -SB On Thu, Feb 6, 2014 at 11:20 AM, Sharath wrote: > hi Vladimir, > > I would like to know if there are any callback mechanism to detect FIFO > errors in NIC ? > could you please let me know. > > Tx > -SB > >

[dpdk-dev] turn on optical bypass

Hi does dpdk provides any API to turn on optical bypass functionality ? please let me know. tx, Sharath

[dpdk-dev] checking packet drop at NIC

hi ! can someone please tell me whether the DPDK provides any method to handle below a. account the packet drops at NIC level ? is there any interrupt raised by DPDK for the same ? b. to check fifo errors ? c. way to check rx and tx in sync Tx, -SB

[dpdk-dev] checking packet drop at NIC

Thanks Daniel ! Let me check it out . . . On Jan 29, 2014 8:54 PM, "Daniel Kaminsky" < daniel.kaminsky at infinitelocality.com> wrote: > Hi Sharath, > > Try rte_eth_stats_get, I think this should give you what you're looking > for. > > Regards, > Da

[dpdk-dev] checking packet drop at NIC

hi! are there any interrupts which are raised by DPDK, for the fifo errors. please let me know, where can I find the details and how to handle such interrupts ? Tx -SB On Thu, Jan 30, 2014 at 2:30 PM, Sharath wrote: > Thanks Daniel ! > Let me check it out . . . > On Jan 29, 201

[dpdk-dev] checking packet drop at NIC

Hi Daniel & all, can anyone please let me know about this. Tx -SB On Thu, Jan 30, 2014 at 4:50 PM, Sharath wrote: > hi! > > are there any interrupts which are raised by DPDK, for the fifo errors. > > please let me know, where can I find the details and how to handle such &g

[dpdk-dev] checking packet drop at NIC

thank you Vladimir. On Fri, Jan 31, 2014 at 12:36 PM, Vladimir Medvedkin wrote: > Hi Sharath, > > In DPDK interrupts are disabled to eliminate the performance overhead. > Interrupts used only for link status change. So you can poll > rte_eth_stats_get and check struct rte_eth_s

[dpdk-dev] compile error on ubuntu 14.4.4 kernel 4.2.0-27-generic in qemu

/rte_eal_memconfig.h:38, from /home/vpptest/vpp/build-root/build-vpp-native/dpdk/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:39: /usr/lib/gcc/x86_64-linux-gnu/4.8/include/emmintrin.h:700:1: note: expected ?__m128i? but argument is of type ?int? Thanks Sharath

[dpdk-dev] compile error on ubuntu 14.4.4 kernel 4.2.0-27-generic in qemu

Root cause: Default cpu config when the VM has be been started by qemu does not support SSE. I have resolved this issue. Here the resolution which I used. Might be helpful for others Method 1 After Configuring VM by GUI based Virtual Machine Manager, go to the CPU config & make SSE as "Required"