From: Minchan Kim <minchan@kernel.org>
To: Oleksandr Natalenko <oleksandr@redhat.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-api@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
Tim Murray <timmurray@google.com>,
Daniel Colascione <dancol@google.com>,
Sandeep Patil <sspatil@google.com>,
Sonny Rao <sonnyrao@google.com>,
Brian Geffon <bgeffon@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Shakeel Butt <shakeelb@google.com>,
John Dias <joaodias@google.com>,
ktkhai@virtuozzo.com, christian.brauner@ubuntu.com,
sjpark@amazon.de
Subject: Re: [PATCH v2 2/5] mm: introduce external memory hinting API
Date: Wed, 22 Jan 2020 17:43:16 -0800 [thread overview]
Message-ID: <20200123014316.GB249784@google.com> (raw)
In-Reply-To: <20200122104424.7gvrfivymjvdous4@butterfly.localdomain>
On Wed, Jan 22, 2020 at 11:44:24AM +0100, Oleksandr Natalenko wrote:
> 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.
Thing is how you could identify a certan range is better for KSM than
others from external process?
next prev parent reply other threads:[~2020-01-23 1:43 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 23:59 [PATCH v2 0/5] introduce memory hinting API for external process Minchan Kim
2020-01-16 23:59 ` [PATCH v2 1/5] mm: factor out madvise's core functionality Minchan Kim
2020-01-17 10:02 ` Kirill Tkhai
2020-01-17 10:02 ` Kirill Tkhai
2020-01-17 18:14 ` Minchan Kim
2020-01-17 18:14 ` Minchan Kim
2020-01-16 23:59 ` [PATCH v2 2/5] mm: introduce external memory hinting API Minchan Kim
2020-01-16 23:59 ` Minchan Kim
2020-01-17 11:52 ` Michal Hocko
2020-01-17 11:52 ` Michal Hocko
2020-01-17 15:58 ` Kirill A. Shutemov
2020-01-17 15:58 ` Kirill A. Shutemov
2020-01-17 17:32 ` Minchan Kim
2020-01-17 17:32 ` Minchan Kim
2020-01-17 21:26 ` Kirill A. Shutemov
2020-01-17 21:26 ` Kirill A. Shutemov
2020-01-18 9:40 ` SeongJae Park
2020-01-18 9:40 ` SeongJae Park
2020-01-19 16:14 ` sspatil
2020-01-19 16:14 ` sspatil-hpIqsD4AKlfQT0dZR+AlfA
2020-01-20 7:58 ` Michal Hocko
2020-01-20 10:39 ` Kirill Tkhai
2020-01-20 10:39 ` Kirill Tkhai
2020-01-21 18:32 ` Minchan Kim
2020-01-22 8:28 ` Michal Hocko
2020-01-22 8:28 ` Michal Hocko
2020-01-22 9:36 ` SeongJae Park
2020-01-22 9:36 ` SeongJae Park
2020-01-22 10:02 ` Michal Hocko
2020-01-22 10:02 ` Michal Hocko
2020-01-22 13:28 ` SeongJae Park
2020-01-22 13:28 ` SeongJae Park
2020-01-23 1:41 ` Minchan Kim
2020-01-23 1:41 ` Minchan Kim
2020-01-23 9:13 ` Michal Hocko
2020-01-21 18:11 ` Minchan Kim
2020-01-21 18:11 ` Minchan Kim
2020-01-22 10:44 ` Oleksandr Natalenko
2020-01-23 1:43 ` Minchan Kim [this message]
2020-01-23 7:29 ` Oleksandr Natalenko
2020-01-17 17:25 ` Minchan Kim
2020-01-17 17:25 ` Minchan Kim
2020-01-20 8:03 ` Michal Hocko
2020-01-20 8:03 ` Michal Hocko
2020-01-20 10:24 ` Kirill Tkhai
2020-01-20 10:24 ` Kirill Tkhai
2020-01-20 11:27 ` Michal Hocko
2020-01-20 11:27 ` Michal Hocko
2020-01-20 12:39 ` Kirill A. Shutemov
2020-01-20 13:24 ` Michal Hocko
2020-01-20 13:24 ` Michal Hocko
2020-01-20 14:21 ` Kirill A. Shutemov
2020-01-20 15:44 ` Michal Hocko
2020-01-20 15:44 ` Michal Hocko
2020-01-21 18:43 ` Minchan Kim
2020-01-21 18:43 ` Minchan Kim
2020-01-16 23:59 ` [PATCH v2 3/5] mm/madvise: employ mmget_still_valid for write lock Minchan Kim
2020-01-16 23:59 ` [PATCH v2 4/5] mm/madvise: allow KSM hints for remote API Minchan Kim
2020-01-17 10:13 ` Kirill Tkhai
2020-01-17 10:13 ` Kirill Tkhai
2020-01-17 12:34 ` Oleksandr Natalenko
2020-01-17 12:34 ` Oleksandr Natalenko
2020-01-21 17:45 ` Minchan Kim
2020-01-21 17:45 ` Minchan Kim
2020-01-16 23:59 ` [PATCH v2 5/5] mm: support both pid and pidfd for process_madvise Minchan Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200123014316.GB249784@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=christian.brauner@ubuntu.com \
--cc=dancol@google.com \
--cc=hannes@cmpxchg.org \
--cc=joaodias@google.com \
--cc=kirill@shutemov.name \
--cc=ktkhai@virtuozzo.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=oleksandr@redhat.com \
--cc=shakeelb@google.com \
--cc=sjpark@amazon.de \
--cc=sonnyrao@google.com \
--cc=sspatil@google.com \
--cc=surenb@google.com \
--cc=timmurray@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.