[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181013112238.GA762@cmpxchg.org>
Date: Sat, 13 Oct 2018 07:22:38 -0400
From: Johannes Weiner <hannes@...xchg.org>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Michal Hocko <mhocko@...nel.org>, linux-mm@...ck.org,
syzkaller-bugs@...glegroups.com, guro@...com,
kirill.shutemov@...ux.intel.com, linux-kernel@...r.kernel.org,
rientjes@...gle.com, yang.s@...baba-inc.com,
Andrew Morton <akpm@...ux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC PATCH] memcg, oom: throttle dump_header for memcg ooms
without eligible tasks
On Sat, Oct 13, 2018 at 08:09:30PM +0900, Tetsuo Handa wrote:
> ---------- Michal's patch ----------
>
> 73133 lines (5.79MB) of kernel messages per one run
>
> [root@...ecurity ~]# time ./a.out
>
> real 3m44.389s
> user 0m0.000s
> sys 3m42.334s
>
> [root@...ecurity ~]# time ./a.out
>
> real 3m41.767s
> user 0m0.004s
> sys 3m39.779s
>
> ---------- My v2 patch ----------
>
> 50 lines (3.40 KB) of kernel messages per one run
>
> [root@...ecurity ~]# time ./a.out
>
> real 0m5.227s
> user 0m0.000s
> sys 0m4.950s
>
> [root@...ecurity ~]# time ./a.out
>
> real 0m5.249s
> user 0m0.000s
> sys 0m4.956s
Your patch is suppressing information that I want to have and my
console can handle, just because your console is slow, even though
there is no need to use that console at that log level.
NAK to your patch. I think you're looking at this from the wrong
angle. A console that takes almost 4 minutes to print 70k lines
shouldn't be the baseline for how verbose KERN_INFO is.
Powered by blists - more mailing lists