Re: [dpdk-users] Linux forcibly descheduling isolated thread on isolated cpu running DPDK rx under load

Hi Terry, Without digging into this too much, it looks like the kernel is context switching out to do a clear_page call, so I wonder if one of your other threads is doing something memory related that's triggering this behaviour. Tim From: users

Re: [dpdk-users] Linux forcibly descheduling isolated thread on isolated cpu running DPDK rx under load

On Thu, 19 Apr 2018 21:01:15 +0100 (BST) "terry.montague.1...@btinternet.com" wrote: > I should also say - I've disabled the kernel's 5% time reservation for > SCHED_FIFO through setting /proc/sys/kernel/sched_rt_runtime_us to -1. > > Any help with this

Re: [dpdk-users] Linux forcibly descheduling isolated thread on isolated cpu running DPDK rx under load

I should also say - I've disabled the kernel's 5% time reservation for SCHED_FIFO through setting /proc/sys/kernel/sched_rt_runtime_us to -1. Any help with this problem gratefully appreciated. Many thanks Terry. Original message >From : terry.montague.1...@btinternet.com Date :

Re: [dpdk-users] DPDK device name

On Thu, 19 Apr 2018 07:15:07 + "Rosen, Rami" wrote: > Hi Flip, > I assume that by "port numbers" you mean the PCI bus id (BDF) > that is used by DPDK (for bind, for example). > > You can fetch the bus id for a netdevice named "eth0" by > ethtool -i eth0 | grep bus-info

[dpdk-users] Linux forcibly descheduling isolated thread on isolated cpu running DPDK rx under load

Hi there, I wondered if anyone had come across this particular problem regarding linux scheduling, or rather what appears to be a forced descheduling effect. I'm running on standard vanilla Ubuntu 17-10 using kernel 4.13.0-36-generic. Local Timer interrupts are therefore enabled I'm running

Re: [dpdk-users] Compilation problems in Ubuntu 16.04 with MLX5 options

Hi, I also encountered a similar problem yesterday with dpdk-17.11 on ubuntu 16.04. I checked my old email from this mailing list, I found a successful solution by reinstall the latest "mlnxofed" by "./mlnxofedinstall --upstream-libs --dpdk" Then you can try to install the dpdk-18.02 and see

Re: [dpdk-users] Compilation problems in Ubuntu 16.04 with MLX5 options

On Wed, Apr 18, 2018 at 08:15:28PM +0200, Andrés Pozo Muñoz wrote: > Hi all, > > I'm trying to build DPDK (tried with 17.11 and 18.02) on Ubuntu 16.04, > with MLX5 support and I'm getting some compilation errors. > The sequence of commands I follow: > > root@olnmalp026Bn001:/usr/src# uname -a >

[dpdk-users] Compilation problems in Ubuntu 16.04 with MLX5 options

Hi all, I'm trying to build DPDK (tried with 17.11 and 18.02) on Ubuntu 16.04, with MLX5 support and I'm getting some compilation errors. The sequence of commands I follow: root@olnmalp026Bn001:/usr/src# uname -a Linux olnmalp026Bn001 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC

Re: [dpdk-users] DPDK device name

Hi Flip, I assume that by "port numbers" you mean the PCI bus id (BDF) that is used by DPDK (for bind, for example). You can fetch the bus id for a netdevice named "eth0" by ethtool -i eth0 | grep bus-info bus-info: :01:00.0 If you mean the internal port number (starting from 0 for the first

Re: [dpdk-users] Flow Director feature on Fortville XL710 adapter not working

Hi Richard, Thank you Richard for replying. As you mentioned, RSS and Flow director won't work simultaneously on a Port. We patched the dpdk rss init (function: i40e_pf_config_rss) code to make it work. In our earlier platform, which uses Intel Niantic, 82599, we were able to make both RSS and

[dpdk-users] DPDK device name

Hi, Is there any mapping between the port names I see while using 'ifconfig' and the port numbers I use normally to handle NIC ports? In other words, is there a way to identify which ports number corresponds to a given linux interface name? Thanks -- BR, Filip +48 666 369 823