[dpdk-dev] [PATCH v2 2/2] kni: add support for core_id param in single threaded mode

Allow binding KNI thread to specific core in single threaded mode by setting core_id and force_bind config parameters. Signed-off-by: Vladyslav Buslov --- v2: * Fixed formatting. * Refactored kthread create/bind functionality into separate function. * Moved thread mode print into kni_init. * Add

[dpdk-dev] [PATCH v2 1/2] kni: add support for core_id param in single threaded mode

Allow binding KNI thread to specific core in single threaded mode by setting core_id and force_bind config parameters. Signed-off-by: Vladyslav Buslov --- lib/librte_eal/linuxapp/kni/kni_misc.c | 48 ++ 1 file changed, 32 insertions(+), 16 deletions(-) diff --git

[dpdk-dev] [PATCH v3] ntnic: add PMD driver

I think that if the driver is just a shim for proprietary code, then the vendor should just maintain it out of tree. 6wind and windriver already do this.

[dpdk-dev] [PATCH v3] ntnic: add PMD driver

2016-09-10 07:58, Finn Christensen: > From: Neil Horman [mailto:nhorman at tuxdriver.com] > > On Fri, Sep 09, 2016 at 12:48:38PM +, Finn Christensen wrote: > > > This is the Napatech NTNIC Poll Mode Driver (PMD) for DPDK. > > > > > > This patch adds support for Napatech NICs to DPDK. This is th

[dpdk-dev] [PATCH] kni: unregister an unregisterd net_device could cause a kernel crash

2016-09-09 14:33, Mcnamara, John: > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon > > 2016-09-08 18:15, Ferruh Yigit: > > > On 9/8/2016 5:44 PM, Stephen Hemminger wrote: > > > > > > ... > > > > > > > But then again the whole KNI driver fails completely when running > > > >

[dpdk-dev] [PATCH v3] ntnic: add PMD driver

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: 9. september 2016 15:51 > To: Finn Christensen > Cc: dev at dpdk.org; thomas.monjalon at 6wind.com; > stephen at networkplumber.org > Subject: Re: [PATCH v3] ntnic: add PMD driver > > On Fri, Sep 09, 2016 at