lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 9 Nov 2017 09:52:49 +0100 From: Michal Hocko <mhocko@...nel.org> To: peter enderborg <peter.enderborg@...ymobile.com> Cc: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>, akpm@...ux-foundation.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Cong Wang <xiyou.wangcong@...il.com>, Dave Hansen <dave.hansen@...el.com>, Johannes Weiner <hannes@...xchg.org>, Mel Gorman <mgorman@...e.de>, Petr Mladek <pmladek@...e.com>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Vlastimil Babka <vbabka@...e.cz>, "yuwang.yuwang" <yuwang.yuwang@...baba-inc.com> Subject: Re: [PATCH] mm: don't warn about allocations which stall for too long [Please try to trim the context you are replying to] On Wed 08-11-17 11:30:23, peter enderborg wrote: [...] > What about the idea to keep the function, but instead of printing only do a trace event. I am not sure. I would rather see a tracepoint to mark the allocator entry. This would allow both 1) measuring the allocation latency (to compare it to the trace_mm_page_alloc and 2) check for stalls with arbitrary user defined timeout (just print all allocations which haven't passed trace_mm_page_alloc for the given amount of time). -- Michal Hocko SUSE Labs
Powered by blists - more mailing lists