From: Christoph Hellwig <hch@infradead.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
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>
Subject: Re: [RFC PATCH 4/4] mm: madvise allow remove operation for hugetlbfs
Date: Thu, 16 Apr 2015 23:44:35 -0700 [thread overview]
Message-ID: <20150417064435.GA21672@infradead.org> (raw)
In-Reply-To: <1429225378-22965-5-git-send-email-mike.kravetz@oracle.com>
On Thu, Apr 16, 2015 at 04:02:58PM -0700, Mike Kravetz wrote:
> Now that we have hole punching support for hugetlbfs, we can
> also support the MADV_REMOVE interface to it.
Meh. Just use fallocate for any new code..
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
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>
Subject: Re: [RFC PATCH 4/4] mm: madvise allow remove operation for hugetlbfs
Date: Thu, 16 Apr 2015 23:44:35 -0700 [thread overview]
Message-ID: <20150417064435.GA21672@infradead.org> (raw)
In-Reply-To: <1429225378-22965-5-git-send-email-mike.kravetz@oracle.com>
On Thu, Apr 16, 2015 at 04:02:58PM -0700, Mike Kravetz wrote:
> Now that we have hole punching support for hugetlbfs, we can
> also support the MADV_REMOVE interface to it.
Meh. Just use fallocate for any new code..
next prev parent reply other threads:[~2015-04-17 6:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 23:02 [RFC PATCH 0/4] hugetlbfs: add fallocate support Mike Kravetz
2015-04-16 23:02 ` Mike Kravetz
2015-04-16 23:02 ` [RFC PATCH 1/4] hugetlbfs: truncate_hugepages() takes a range of pages Mike Kravetz
2015-04-16 23:02 ` Mike Kravetz
2015-04-16 23:02 ` [RFC PATCH 2/4] hugetlbfs: New huge_add_to_page_cache helper routine Mike Kravetz
2015-04-16 23:02 ` Mike Kravetz
2015-04-16 23:02 ` [RFC PATCH 3/4] hugetlbfs: add hugetlbfs_fallocate() Mike Kravetz
2015-04-16 23:02 ` Mike Kravetz
2015-04-16 23:02 ` [RFC PATCH 4/4] mm: madvise allow remove operation for hugetlbfs Mike Kravetz
2015-04-16 23:02 ` Mike Kravetz
2015-04-17 6:44 ` Christoph Hellwig [this message]
2015-04-17 6:44 ` Christoph Hellwig
2015-04-17 16:53 ` Mike Kravetz
2015-04-17 16:53 ` Mike Kravetz
[not found] <00e601d078da$9e762190$db6264b0$@alibaba-inc.com>
2015-04-17 7:10 ` Hillf Danton
2015-04-17 7:10 ` Hillf Danton
2015-04-17 17:11 ` Mike Kravetz
2015-04-17 17:11 ` Mike Kravetz
2015-04-18 16:16 ` Mike Kravetz
2015-04-18 16:16 ` Mike Kravetz
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=20150417064435.GA21672@infradead.org \
--to=hch@infradead.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--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 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.