Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On (12/14/16 13:36), Petr Mladek wrote:
[..]
> [*] The async printk patchset is flying around in many
>     modifications for years. I am more optimistic after
>     the discussions on the last Kernel Summit. Anyway,
>     it will not be in mainline before 4.12.
> 
> [**] printk_deferred() only puts massages into the log
>      buffer. It does not call
>      console_trylock()/console_unlock(). Therefore,
>      it is always "fast".

a small addition,

as a side effect, printk_deferred()  guarantees  that we will
attempt to console_unlock() from IRQ. CPU's pending bit stays
set until we run the irq work list on that CPU, per-CPU irq
work stays queued in per-CPU irq work list.

so, yes, printk_deferred() adds messages to logbuf, but in
exchange it says:
    "I promise I will try to do console_unlock() from IRQ".

	-ss

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]