From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: 'Mike Kravetz' <mike.kravetz@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: 'Dave Hansen' <dave.hansen@linux.intel.com>,
'Naoya Horiguchi' <n-horiguchi@ah.jp.nec.com>,
'David Rientjes' <rientjes@google.com>,
'Hugh Dickins' <hughd@google.com>,
'Davidlohr Bueso' <dave@stgolabs.net>,
'Aneesh Kumar' <aneesh.kumar@linux.vnet.ibm.com>,
'Christoph Hellwig' <hch@infradead.org>
Subject: Re: [RFC v2 PATCH 0/5] hugetlbfs: add fallocate support
Date: Wed, 29 Apr 2015 15:04:02 +0800 [thread overview]
Message-ID: <016801d0824a$ace5da80$06b18f80$@alibaba-inc.com> (raw)
In-Reply-To: <1429827197-677-1-git-send-email-mike.kravetz@oracle.com>
>
> hugetlbfs is used today by applications that want a high degree of
> control over huge page usage. Often, large hugetlbfs files are used
> to map a large number huge pages into the application processes.
> The applications know when page ranges within these large files will
> no longer be used, and ideally would like to release them back to
> the subpool or global pools for other uses. The fallocate() system
> call provides an interface for preallocation and hole punching within
> files. This patch set adds fallocate functionality to hugetlbfs.
>
> RFC v2:
> Addressed alignment and error handling issues noticed by Hillf Danton
> New region_del() routine for region tracking/resv_map of ranges
> Fixed several issues found during more extensive testing
> Error handling in region_del() when kmalloc() fails stills needs
> to be addressed
> madvise remove support remains
>
> Mike Kravetz (5):
> hugetlbfs: truncate_hugepages() takes a range of pages
> hugetlbfs: remove region_truncte() as region_del() can be used
> hugetlbfs: New huge_add_to_page_cache helper routine
> hugetlbfs: add hugetlbfs_fallocate()
> mm: madvise allow remove operation for hugetlbfs
>
Acked-by: Hillf Danton <hillf.zj@alibaba-inc.com>
> fs/hugetlbfs/inode.c | 169 ++++++++++++++++++++++++++++++++++++++++++++++--
> include/linux/hugetlb.h | 8 ++-
> mm/hugetlb.c | 110 ++++++++++++++++++++++---------
> mm/madvise.c | 2 +-
> 4 files changed, 248 insertions(+), 41 deletions(-)
>
> --
> 2.1.0
--
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>
prev parent reply other threads:[~2015-04-29 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 22:13 [RFC v2 PATCH 0/5] hugetlbfs: add fallocate support Mike Kravetz
2015-04-23 22:13 ` [RFC v2 PATCH 1/5] hugetlbfs: truncate_hugepages() takes a range of pages Mike Kravetz
2015-04-23 22:13 ` [RFC v2 PATCH 2/5] hugetlbfs: remove region_truncte() as region_del() can be used Mike Kravetz
2015-04-23 22:13 ` [RFC v2 PATCH 3/5] hugetlbfs: New huge_add_to_page_cache helper routine Mike Kravetz
2015-04-23 22:13 ` [RFC v2 PATCH 4/5] hugetlbfs: add hugetlbfs_fallocate() Mike Kravetz
2015-04-23 22:13 ` [RFC v2 PATCH 5/5] mm: madvise allow remove operation for hugetlbfs Mike Kravetz
2015-04-29 7:04 ` Hillf Danton [this message]
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='016801d0824a$ace5da80$06b18f80$@alibaba-inc.com' \
--to=hillf.zj@alibaba-inc.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@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 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).