] Kernel deadlock due to rte_kni
On Thu, Mar 26, 2015 at 11:01:14AM +, Dey, Souvik wrote:
> Do you see any benefit of calling netif_rx_ni() and not directly netif_rx() ?
>
Yes, I see using the ni variant as not being a bug. kni_net_rx is run from
process context (it runs as a thread c
Do you see any benefit of calling netif_rx_ni() and not directly netif_rx() ?
-Original Message-
From: Neil Horman [mailto:nhor...@tuxdriver.com]
Sent: Thursday, March 26, 2015 4:16 PM
To: Dey, Souvik
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Kernel deadlock due to rte_kni
On Wed, Mar
On Thu, Mar 26, 2015 at 11:01:14AM +, Dey, Souvik wrote:
> Do you see any benefit of calling netif_rx_ni() and not directly netif_rx() ?
>
Yes, I see using the ni variant as not being a bug. kni_net_rx is run from
process context (it runs as a thread created by kthread_create). netif_rx
On Wed, Mar 25, 2015 at 07:39:49PM +, Dey, Souvik wrote:
> Hi All,
> There looks like an issue will rte_kni.ko which gets kernel
> into deadlock. We are trying to run rte_kni.ko with multiple thread support
> which are pinned to different non-isolated cores. When we test with
Hi All,
There looks like an issue will rte_kni.ko which gets kernel
into deadlock. We are trying to run rte_kni.ko with multiple thread support
which are pinned to different non-isolated cores. When we test with tcp/tls the
kernel is getting hanged in on race condition. Below is
http://patchwork.dpdk.org/ml/archives/dev/2015-February/013335.html
Jay
On Wed, Mar 25, 2015 at 2:39 PM, Dey, Souvik wrote:
> Hi All,
> There looks like an issue will rte_kni.ko which gets
> kernel into deadlock. We are trying to run rte_kni.ko with multiple thread
> support
6 matches
Mail list logo
