[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKOZuetLW31vrsxndrH7gVh5er+J5DepBY6XcfxnFmZQaLWhrQ@mail.gmail.com>
Date: Thu, 5 Sep 2019 15:51:19 -0700
From: Daniel Colascione <dancol@...gle.com>
To: Tom Zanussi <zanussi@...nel.org>
Cc: Joel Fernandes <joel@...lfernandes.org>,
Steven Rostedt <rostedt@...dmis.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Michal Hocko <mhocko@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Tim Murray <timmurray@...gle.com>,
Carmen Jackson <carmenjackson@...gle.com>,
Mayank Gupta <mayankgupta@...gle.com>,
Minchan Kim <minchan@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
kernel-team <kernel-team@...roid.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
Dan Williams <dan.j.williams@...el.com>,
Jerome Glisse <jglisse@...hat.com>,
linux-mm <linux-mm@...ck.org>,
Matthew Wilcox <willy@...radead.org>,
Ralph Campbell <rcampbell@...dia.com>,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH v2] mm: emit tracepoint when RSS changes by threshold
On Thu, Sep 5, 2019 at 3:12 PM Daniel Colascione <dancol@...gle.com> wrote:
> Basically, what I have in mind is this:
Actually --- I wonder whether there's already enough power in the
trigger mechanism to do this without any code changes to ftrace
histograms themselves. I'm trying to think of the minimum additional
kernel facility that we'd need to implement the scheme I described
above, and it might be that we don't need to do anything at all except
add the actual level tracepoints.
Powered by blists - more mailing lists