[PATCH 4/4] printk: Use unbound irq work for printing and waking

Now when per-cpu printk buffers are gone, there's no need to have printk flags or printk irq_work per cpu. Just make printk_pending a single variable operated by atomic operations and have single unbound irq work doing the waking and printing. This has an advantage that any cpu can do the printing

Re: [PATCH 4/4] printk: Use unbound irq work for printing and waking

On Wed, 21 Aug 2013 10:08:32 +0200 Jan Kara wrote: > Now when per-cpu printk buffers are gone, there's no need to have printk > flags or printk irq_work per cpu. Just make printk_pending a single > variable operated by atomic operations and have single unbound irq work > doing the waking and prin

[PATCH 4/4] printk: Use unbound irq work for printing and waking

Now when per-cpu printk buffers are gone, there's no need to have printk flags or printk irq_work per cpu. Just make printk_pending a single variable operated by atomic operations and have single unbound irq work doing the waking and printing. This has an advantage that any cpu can do the printing

[PATCH 4/4] printk: Use unbound irq work for printing and waking

Now when per-cpu printk buffers are gone, there's no need to have printk flags or printk irq_work per cpu. Just make printk_pending a single variable operated by atomic operations and have single unbound irq work doing the waking and printing. This has an advantage that any cpu can do the printing