From: Andi Kleen <andi@firstfloor.org>
To: Shaohua Li <shli@fb.com>
Cc: linux-mm@kvack.org, linux-api@vger.kernel.org,
Kernel-team@fb.com, Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
Minchan Kim <minchan@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH V4][for-next]mm: add a new vector based madvise syscall
Date: Fri, 11 Dec 2015 19:31:33 +0100 [thread overview]
Message-ID: <20151211183133.GR15533@two.firstfloor.org> (raw)
In-Reply-To: <d01698140a51cf9b2ce233c7574c2ece9f6fa241.1449791762.git.shli@fb.com>
On Thu, Dec 10, 2015 at 04:03:37PM -0800, Shaohua Li wrote:
> In jemalloc, a free(3) doesn't immediately free the memory to OS even
> the memory is page aligned/size, and hope the memory can be reused soon.
> Later the virtual address becomes fragmented, and more and more free
> memory are aggregated. If the free memory size is large, jemalloc uses
> madvise(DONT_NEED) to actually free the memory back to OS.
>
Looks good to me now.
-Andi
--
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:[~2015-12-11 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 0:03 [PATCH V4][for-next]mm: add a new vector based madvise syscall Shaohua Li
2015-12-11 0:03 ` Shaohua Li
2015-12-11 18:31 ` Andi Kleen [this message]
2016-01-11 19:00 ` Shaohua Li
[not found] ` <20160111190021.GA3589410-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2016-01-11 19:06 ` Andrew Morton
2016-01-11 19:06 ` Andrew Morton
[not found] ` <d01698140a51cf9b2ce233c7574c2ece9f6fa241.1449791762.git.shli-b10kYP2dOMg@public.gmane.org>
2016-02-17 0:08 ` Andrew Morton
2016-02-17 0:08 ` Andrew Morton
2016-02-17 17:47 ` Shaohua Li
[not found] ` <20160217174654.GA3505386-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2016-02-18 12:38 ` Michael Kerrisk (man-pages)
2016-02-18 12:38 ` Michael Kerrisk (man-pages)
2016-03-08 22:37 ` Shaohua Li
2016-03-08 22:37 ` Shaohua Li
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=20151211183133.GR15533@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Kernel-team@fb.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=shli@fb.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.