From: Michal Hocko <mhocko@kernel.org>
To: peter enderborg <peter.enderborg@sonymobile.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Cong Wang <xiyou.wangcong@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
"yuwang.yuwang" <yuwang.yuwang@alibaba-inc.com>
Subject: Re: [PATCH] mm: don't warn about allocations which stall for too long
Date: Thu, 9 Nov 2017 09:52:49 +0100 [thread overview]
Message-ID: <20171109085249.guihvx5tzm77u3qk@dhcp22.suse.cz> (raw)
In-Reply-To: <91bdbdea-3f33-b7c0-8345-d0fa8c7f1cf1@sonymobile.com>
[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
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: peter enderborg <peter.enderborg@sonymobile.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Cong Wang <xiyou.wangcong@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
"yuwang.yuwang" <yuwang.yuwang@alibaba-inc.com>
Subject: Re: [PATCH] mm: don't warn about allocations which stall for too long
Date: Thu, 9 Nov 2017 09:52:49 +0100 [thread overview]
Message-ID: <20171109085249.guihvx5tzm77u3qk@dhcp22.suse.cz> (raw)
In-Reply-To: <91bdbdea-3f33-b7c0-8345-d0fa8c7f1cf1@sonymobile.com>
[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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-09 8:52 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 11:28 [PATCH] mm: don't warn about allocations which stall for too long Tetsuo Handa
2017-10-26 11:28 ` Tetsuo Handa
2017-10-26 11:41 ` Michal Hocko
2017-10-26 11:41 ` Michal Hocko
2017-11-08 10:30 ` peter enderborg
2017-11-09 8:52 ` Michal Hocko [this message]
2017-11-09 8:52 ` Michal Hocko
2017-11-09 9:34 ` peter enderborg
2017-11-09 10:09 ` Michal Hocko
2017-11-09 10:09 ` Michal Hocko
2017-11-09 10:19 ` Tetsuo Handa
2017-11-09 10:19 ` Tetsuo Handa
2017-10-26 14:37 ` Johannes Weiner
2017-10-26 14:37 ` Johannes Weiner
2017-10-31 19:32 ` Steven Rostedt
2017-11-01 8:30 ` Vlastimil Babka
2017-11-01 8:30 ` Vlastimil Babka
2017-11-01 13:38 ` Petr Mladek
2017-11-01 13:38 ` Petr Mladek
2017-11-01 15:36 ` Steven Rostedt
2017-11-01 15:36 ` Steven Rostedt
2017-11-02 11:46 ` Petr Mladek
2017-11-02 11:46 ` Petr Mladek
2017-11-02 14:49 ` Steven Rostedt
2017-11-02 14:49 ` Steven Rostedt
2017-11-01 15:33 ` Steven Rostedt
2017-11-01 15:33 ` Steven Rostedt
2017-11-01 17:42 ` Vlastimil Babka
2017-11-01 17:42 ` Vlastimil Babka
2017-11-01 17:54 ` Steven Rostedt
2017-11-01 17:54 ` Steven Rostedt
2017-11-02 8:53 ` Sergey Senozhatsky
2017-11-02 8:53 ` Sergey Senozhatsky
2017-11-02 9:14 ` Sergey Senozhatsky
2017-11-02 9:14 ` Sergey Senozhatsky
2017-11-02 14:55 ` Steven Rostedt
2017-11-02 14:55 ` Steven Rostedt
2017-11-02 12:55 ` Michal Hocko
2017-11-02 12:55 ` Michal Hocko
2017-11-02 15:56 ` Steven Rostedt
2017-11-02 15:56 ` Steven Rostedt
2017-11-02 17:06 ` [PATCH v2] printk: Add console owner and waiter logic to load balance console writes Steven Rostedt
2017-11-02 17:06 ` Steven Rostedt
2017-11-02 17:10 ` Steven Rostedt
2017-11-02 17:10 ` Steven Rostedt
2017-11-02 17:38 ` Steven Rostedt
2017-11-02 17:38 ` Steven Rostedt
2017-11-03 10:19 ` Jan Kara
2017-11-03 10:19 ` Jan Kara
2017-11-03 11:18 ` Steven Rostedt
2017-11-03 11:18 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171109085249.guihvx5tzm77u3qk@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peter.enderborg@sonymobile.com \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=vbabka@suse.cz \
--cc=xiyou.wangcong@gmail.com \
--cc=yuwang.yuwang@alibaba-inc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.