[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200122104424.7gvrfivymjvdous4@butterfly.localdomain>
Date: Wed, 22 Jan 2020 11:44:24 +0100
From: Oleksandr Natalenko <oleksandr@...hat.com>
To: Minchan Kim <minchan@...nel.org>
Cc: "Kirill A. Shutemov" <kirill@...temov.name>,
Michal Hocko <mhocko@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, linux-api@...r.kernel.org,
Suren Baghdasaryan <surenb@...gle.com>,
Tim Murray <timmurray@...gle.com>,
Daniel Colascione <dancol@...gle.com>,
Sandeep Patil <sspatil@...gle.com>,
Sonny Rao <sonnyrao@...gle.com>,
Brian Geffon <bgeffon@...gle.com>,
Johannes Weiner <hannes@...xchg.org>,
Shakeel Butt <shakeelb@...gle.com>,
John Dias <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
Hello.
On Tue, Jan 21, 2020 at 10:11:13AM -0800, Minchan Kim wrote:
> > > I also think people don't want to give an KSM hint to non-mergeable area.
> >
> > And how the manager knows which data is mergable?
>
> Oleksandr, could you say your thought why you need address range based
> API?
It seems I've overlooked an important piece of this submission: one
cannot apply the hint to all the anonymous mapping regardless of address
range. For KSM I'd rather either have a possibility to hint all the
anonymous mappings, or, as it was suggested previously, be able to iterate
over existing mappings using some (fd-based?) API.
--
Best regards,
Oleksandr Natalenko (post-factum)
Senior Software Maintenance Engineer
Powered by blists - more mailing lists