From: Dave Hansen <dave.hansen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>, Aaron Lu <aaron.lu@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Tim Chen <tim.c.chen@intel.com>,
Ying Huang <ying.huang@intel.com>
Subject: Re: [PATCH 0/5] mm: support parallel free of memory
Date: Tue, 28 Feb 2017 16:43:45 -0800 [thread overview]
Message-ID: <b20b53b5-346e-3558-2260-44b3d111636b@intel.com> (raw)
In-Reply-To: <20170228163947.cbd83e48dcb149c697b316cd@linux-foundation.org>
On 02/28/2017 04:39 PM, Andrew Morton wrote:
> Dumb question: why not do this in userspace, presumably as part of the
> malloc() library? malloc knows where all the memory is and should be
> able to kick off N threads to run around munmapping everything?
One of the places we saw this happen was when an app crashed and was
exit()'ing under duress without cleaning up nicely. The time that it
takes to unmap a few TB of 4k pages is pretty excessive.
--
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:[~2017-03-01 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 11:40 Aaron Lu
2017-02-24 11:40 ` [PATCH 1/5] mm: add tlb_flush_mmu_free_batches Aaron Lu
2017-02-24 11:40 ` [PATCH 2/5] mm: parallel free pages Aaron Lu
2017-02-24 11:40 ` [PATCH 3/5] mm: use a dedicated workqueue for the free workers Aaron Lu
2017-02-24 11:40 ` [PATCH 4/5] mm: add force_free_pages in zap_pte_range Aaron Lu
2017-02-24 11:40 ` [PATCH 5/5] mm: add debugfs interface for parallel free tuning Aaron Lu
2017-03-01 0:39 ` [PATCH 0/5] mm: support parallel free of memory Andrew Morton
2017-03-01 0:43 ` Dave Hansen [this message]
2017-03-01 1:17 ` Aaron Lu
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=b20b53b5-346e-3558-2260-44b3d111636b@intel.com \
--to=dave.hansen@intel.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tim.c.chen@intel.com \
--cc=ying.huang@intel.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