Re: [PATCH] lightnvm: update closed list out of interrupt context

2016-01-26 Thread Matias Bjørling
On 01/25/2016 12:58 PM, Javier González wrote: > When an I/O finishes, full blocks are moved from the open to the closed > list - a lock is taken to protect the list. This happens at the moment > in the interrupt context, which is not correct. > > This patch moves this logic to the GC workqueue

Re: [PATCH] lightnvm: update closed list out of interrupt context

2016-01-26 Thread Matias Bjørling
On 01/25/2016 12:58 PM, Javier González wrote: > When an I/O finishes, full blocks are moved from the open to the closed > list - a lock is taken to protect the list. This happens at the moment > in the interrupt context, which is not correct. > > This patch moves this logic to the GC workqueue

[PATCH] lightnvm: update closed list out of interrupt context

2016-01-25 Thread Javier González
When an I/O finishes, full blocks are moved from the open to the closed list - a lock is taken to protect the list. This happens at the moment in the interrupt context, which is not correct. This patch moves this logic to the GC workqueue instead, thus avoiding holding a spinlock in an atomic

[PATCH] lightnvm: update closed list out of interrupt context

2016-01-25 Thread Javier González
When an I/O finishes, full blocks are moved from the open to the closed list - a lock is taken to protect the list. This happens at the moment in the interrupt context, which is not correct. This patch moves this logic to the GC workqueue instead, thus avoiding holding a spinlock in an atomic