Re: [PATCH v17 1/7] mm: support madvise(MADV_FREE)
From: Michal Hocko <hidden>
Date: 2014-12-02 10:01:31
Also in:
linux-mm, lkml
On Mon 01-12-14 08:56:52, Minchan Kim wrote: [...]
quoted hunk ↗ jump to hunk
From 2edd6890f92fa4943ce3c452194479458582d88c Mon Sep 17 00:00:00 2001 From: Minchan Kim <minchan@kernel.org> Date: Mon, 1 Dec 2014 08:53:55 +0900 Subject: [PATCH] madvise.2: Document MADV_FREE Signed-off-by: Minchan Kim <minchan@kernel.org> --- man2/madvise.2 | 13 +++++++++++++ 1 file changed, 13 insertions(+)diff --git a/man2/madvise.2 b/man2/madvise.2 index 032ead7..33aa936 100644 --- a/man2/madvise.2 +++ b/man2/madvise.2@@ -265,6 +265,19 @@ file (see .BR MADV_DODUMP " (since Linux 3.4)" Undo the effect of an earlier .BR MADV_DONTDUMP . +.TP +.BR MADV_FREE " (since Linux 3.19)" +Gives the VM system the freedom to free pages, and tells the system that +information in the specified page range is no longer important. +This is an efficient way of allowing +.BR malloc (3)
This might be rather misleading. Only some malloc implementations are using this feature (jemalloc, right?). So either be specific about which implementation or do not add it at all.
+to free pages anywhere in the address space, while keeping the address space +valid. The next time that the page is referenced, the page might be demand +zeroed, or might contain the data that was there before the MADV_FREE call. +References made to that address space range will not make the VM system page the +information back in from backing store until the page is modified again.
I am not sure I understand the last sentence. So say I did MADV_FREE and the reclaim has dropped that page. I know that the file backed mappings are not supported yet but assume they were for a second... Now, I do read from that location again what is the result? If we consider anon mappings then the backing store is misleading as well because memory was dropped and so always newly allocated. I would rather drop the whole sentence and rather see an explanation what is the difference between to MADV_DONT_NEED. " Unlike MADV_DONT_NEED the memory is freed lazily e.g. when the VM system is under memory pressure. "
+It works only with private anonymous pages (see +.BR mmap (2)). .SH RETURN VALUE On success .BR madvise ()
-- 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>