[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200123091339.GI29276@dhcp22.suse.cz>
Date: Thu, 23 Jan 2020 10:13:39 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Minchan Kim <minchan@...nel.org>
Cc: sspatil@...gle.com, kirill@...temov.name,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-api@...r.kernel.org,
oleksandr@...hat.com, surenb@...gle.com, timmurray@...gle.com,
dancol@...gle.com, sonnyrao@...gle.com, bgeffon@...gle.com,
hannes@...xchg.org, shakeelb@...gle.com, joaodias@...gle.com,
ktkhai@...tuozzo.com, christian.brauner@...ntu.com,
sjpark@...zon.de
Subject: Re: [PATCH v2 2/5] mm: introduce external memory hinting API
On Wed 22-01-20 17:41:31, Minchan Kim wrote:
[...]
> What do you want to see further?
Either a consensus that it is sufficient to have an inherently racy
interface that requires some form of external sychronization or
a robust interface that can cope with races in a sensible way.
And no, having a flag for future extension is definitely not the
way how a new API should be added. Seriously!
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists