On Thu, 2 Feb 2017, Waiman Long wrote:
> For spinlock and read-write locks, both *_unlock() and *_unlock_irq()
> functions are inlined if !PREEMPT. Whereas the *_unlock_bh() and
> *unlock_irqrestore() are not inlined as that will increase the size
> of the kernel binary.
>
> Given the fact that
On Thu, 2 Feb 2017, Waiman Long wrote:
> For spinlock and read-write locks, both *_unlock() and *_unlock_irq()
> functions are inlined if !PREEMPT. Whereas the *_unlock_bh() and
> *unlock_irqrestore() are not inlined as that will increase the size
> of the kernel binary.
>
> Given the fact that
For spinlock and read-write locks, both *_unlock() and *_unlock_irq()
functions are inlined if !PREEMPT. Whereas the *_unlock_bh() and
*unlock_irqrestore() are not inlined as that will increase the size
of the kernel binary.
Given the fact that the PV qspinlock unlock call is a callee-saved
For spinlock and read-write locks, both *_unlock() and *_unlock_irq()
functions are inlined if !PREEMPT. Whereas the *_unlock_bh() and
*unlock_irqrestore() are not inlined as that will increase the size
of the kernel binary.
Given the fact that the PV qspinlock unlock call is a callee-saved
4 matches
Mail list logo