Re: [PATCH net-next v2] net: sched: don't disable bh when accessing action idr

Mon, May 21, 2018 at 10:03:04PM CEST, vla...@mellanox.com wrote: >Initial net_device implementation used ingress_lock spinlock to synchronize >ingress path of device. This lock was used in both process and bh context. >In some code paths action map lock was obtained while holding ingress_lock.

Re: [PATCH net-next v2] net: sched: don't disable bh when accessing action idr

On Wed 23 May 2018 at 01:10, Cong Wang wrote: > On Mon, May 21, 2018 at 1:03 PM, Vlad Buslov wrote: >> Initial net_device implementation used ingress_lock spinlock to synchronize >> ingress path of device. This lock was used in both process and bh

Re: [PATCH net-next v2] net: sched: don't disable bh when accessing action idr

On Mon, May 21, 2018 at 1:03 PM, Vlad Buslov wrote: > Initial net_device implementation used ingress_lock spinlock to synchronize > ingress path of device. This lock was used in both process and bh context. > In some code paths action map lock was obtained while holding

Re: [PATCH net-next v2] net: sched: don't disable bh when accessing action idr

On 21/05/18 04:03 PM, Vlad Buslov wrote: Initial net_device implementation used ingress_lock spinlock to synchronize ingress path of device. This lock was used in both process and bh context. In some code paths action map lock was obtained while holding ingress_lock. Commit e1e992e52faa

[PATCH net-next v2] net: sched: don't disable bh when accessing action idr

Initial net_device implementation used ingress_lock spinlock to synchronize ingress path of device. This lock was used in both process and bh context. In some code paths action map lock was obtained while holding ingress_lock. Commit e1e992e52faa ("[NET_SCHED] protect action config/dump from