Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1617877 > unrolled thread

Re: [PATCH v8] mm: Add memory allocation watchdog kernel thread.

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v8] mm: Add memory allocation watchdog kernel thread. Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2017-04-06 13:10 +0200

#1617877 — Re: [PATCH v8] mm: Add memory allocation watchdog kernel thread.

Andrew, anything else I can do?

Tetsuo Handa wrote:
>   Regarding maintenance burden, I consider this patch is least invasive
>   because it does not make __GFP_NOWARN flag's semantic confusing while
>   providing administrators some hints [4]. Also, this patch will remain
>   useful because we might overlook something that can cause infinite
>   loop (or significant delay) in future changes, and we can remove this
>   patch when we achieve safe and robust memory management subsystem.
> 
> Changes from v7 [11]:
> 
>   (1) Reflect review comments from Andrew Morton. (Convert "u8 type" to
>       "bool report", use CPUHP_PAGE_ALLOC_DEAD event and replace
>       for_each_possible_cpu() with for_each_online_cpu(), reuse existing
>       rcu_lock_break() and hung_timeout_jiffies() for now, update comments).

We are still sometimes overlooking unexpected delays like
http://lkml.kernel.org/r/alpine.LSU.2.11.1704051331420.4288@eggly.anvils and
http://lkml.kernel.org/r/da13c3c7-b514-67b0-2eb9-6d6af277901b@wiesinger.com
and I think we will in the future. I believe that this patch is helpful for
catching such cases.

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web