From: Michal Hocko <mhocko@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@surriel.com>
Subject: Re: [LSF/MM TOPIC] few MM topics
Date: Thu, 25 Jan 2018 11:02:19 +0100 [thread overview]
Message-ID: <20180125100219.GO28465@dhcp22.suse.cz> (raw)
In-Reply-To: <bee1d564-b4b8-ed0c-edfa-f6df6a24fe21@oracle.com>
On Wed 24-01-18 10:23:20, Mike Kravetz wrote:
> On 01/24/2018 01:26 AM, Michal Hocko wrote:
[...]
> > - It seems there is some demand for large (> MAX_ORDER) allocations.
> > We have that alloc_contig_range which was originally used for CMA and
> > later (ab)used for Giga hugetlb pages. The API is less than optimal
> > and we should probably think about how to make it more generic.
>
> This is also of interest to me. I actually started some efforts in this
> area. The idea (as you mention above) would be to provide a more usable
> API for allocation of contiguous pages/ranges. And, gigantic huge pages
> would be the first consumer.
>
> alloc_contig_range currently has some issues with being used in a 'more
> generic' way. A comment describing the routine says "it's the caller's
> responsibility to guarantee that we are the only thread that changes
> migrate type of pageblocks the pages fall in.". This is true, and I think
> it also applies to users of the underlying routines such as
> start_isolate_page_range. The CMA code has a mechanism that prevents two
> threads from operating on the same range concurrently. The other users
> (gigantic page allocation and memory offline) happen infrequently enough
> that we are unlikely to have a conflict. But, opening this up to more
> generic use will require at least a more generic synchronization mechanism.
Yes, that is exactly my concern and the current state of art that has to
change. I am not yet sure how. So any discussion seems interesting.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-25 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 9:26 [LSF/MM TOPIC] few MM topics Michal Hocko
2018-01-24 18:23 ` Mike Kravetz
2018-01-25 10:02 ` Michal Hocko [this message]
2018-01-25 9:37 ` Jan Kara
2018-01-31 19:21 ` Darrick J. Wong
2018-01-31 20:24 ` Michal Hocko
2018-01-31 23:41 ` Dave Chinner
2018-02-01 15:46 ` [Lsf-pc] " Michal Hocko
2018-02-01 22:47 ` Dave Chinner
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=20180125100219.GO28465@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mike.kravetz@oracle.com \
--cc=riel@surriel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).