[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALvZod4xDNSAHuoAyJHtAccELOeM0pAc30mJ_-ahkK2KPDJVPg@mail.gmail.com>
Date: Thu, 24 Jun 2021 07:34:39 -0700
From: Shakeel Butt <shakeelb@...gle.com>
To: SeongJae Park <sj38.park@...il.com>
Cc: SeongJae Park <sjpark@...zon.de>, Jonathan.Cameron@...wei.com,
acme@...nel.org, alexander.shishkin@...ux.intel.com,
amit@...nel.org, benh@...nel.crashing.org,
Brendan Higgins <brendanhiggins@...gle.com>,
Jonathan Corbet <corbet@....net>,
David Hildenbrand <david@...hat.com>, dwmw@...zon.com,
Marco Elver <elver@...gle.com>, "Du, Fan" <fan.du@...el.com>,
foersleo@...zon.de, greg@...ah.com,
Greg Thelen <gthelen@...gle.com>, guoju.fgj@...baba-inc.com,
jgowans@...zon.com, Mel Gorman <mgorman@...e.de>, mheyne@...zon.de,
Minchan Kim <minchan@...nel.org>,
Ingo Molnar <mingo@...hat.com>, namhyung@...nel.org,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Rik van Riel <riel@...riel.com>,
David Rientjes <rientjes@...gle.com>,
Steven Rostedt <rostedt@...dmis.org>,
Mike Rapoport <rppt@...nel.org>, Shuah Khan <shuah@...nel.org>,
sieberf@...zon.com, snu@...le79.org,
Vlastimil Babka <vbabka@...e.cz>,
Vladimir Davydov <vdavydov.dev@...il.com>,
zgf574564920@...il.com, linux-damon@...zon.com,
Linux MM <linux-mm@...ck.org>, linux-doc@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v31 01/13] mm: Introduce Data Access MONitor (DAMON)
On Thu, Jun 24, 2021 at 3:26 AM SeongJae Park <sj38.park@...il.com> wrote:
>
[...]
> > > if time() % update_interval == 0:
> >
> > regions_update_interval?
>
> It used the name before. But, I changed the name in this way to use it as a
> general periodic updates of monitoring primitives. Of course we can use the
> specific name only in this specific example, but also want to make this as
> similar to the actual code as possible.
>
> If you strongly want to rename this, please feel free to let me know.
>
Nah, it is ok.
[...]
> >
> > Any reason to not use kthread_stop() here?
>
> Using 'kthread_stop()' here will make the code much simpler. But, 'kdamond'
> also stops itself when all monitoring targets became invalid (e.g., all
> monitoring target processes terminated). However, 'kthread_stop()' is not easy
> to be used for the use case (self stopping). It's of course possible, but it
> would make the code longer. That's why I use 'kdamond_stop' flag here. So,
> I'd like leave this as is. If you think 'kthread_stop()' should be used,
> please feel free to let me know.
>
Fine as it is.
Powered by blists - more mailing lists