Add kmalloc failover to vmalloc
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · ----- On Sep 21, 2017, at 2:29 PM, Michael Jeanson [email protected] wrote:
This patch is based on the kvmalloc helpers introduced in kernel 4.12.
It will gracefully failover memory allocations of more than one page to vmalloc for systems under high memory pressure or fragmentation.
I only used it in
lttng-events.cas a POC, most allocations fit into a single page so I'm not sure how useful this actually is.Thoughts?
Just update the changelog to specify why we need this for struct lttng_session (~32kB), and you can submit it for good with a "Fix: " tag.
Thanks,
Mathieu
Quoted 226 lines
V2:
- Addvmalloc_sync_all
- Use only forlttng_sessionSigned-off-by Michael Jeanson <[email protected]>See upstream commit:
commita7c3e901a46ff54c016d040847eda598a9e3e653
Author: Michal Hocko <[email protected]>
Date: Mon May 8 15:57:09 2017 -0700mm: introduce kv[mz]alloc helpers
Patch series "kvmalloc", v5.
There are many open coded kmalloc with vmalloc fallback instances in the tree. Most of them are not careful enough or simply do not care about the underlying semantic of the kmalloc/page allocator which means that
a) some vmalloc fallbacks are basically unreachable because the kmalloc part will keep retrying until it succeeds b) the page allocator can invoke a really disruptive steps like the OOM killer to move forward which doesn't sound appropriate when we consider that the vmalloc fallback is available.As it can be seen implementing kvmalloc requires quite an intimate knowledge if the page allocator and the memory reclaim internals which strongly suggests that a helper should be implemented in the memory subsystem proper.
Most callers, I could find, have been converted to use the helper instead. This is patch 6. There are some more relying on
__GFP_REPEATin the networking stack which I have converted as well and Eric Dumazet was not opposed [2] to convert them as well.[1] http://lkml.kernel.org/r/[email protected]
[2]
http://lkml.kernel.org/r/1485273626.16328.301.camel@edumazet-glaptop3.roam.corp.google.comThis patch (of 9):
Using kmalloc with the vmalloc fallback for larger allocations is a common pattern in the kernel code. Yet we do not have any common helper for that and so users have invented their own helpers. Some of them are really creative when doing so. Let's just add kv[mz]alloc and make sure it is implemented properly. This implementation makes sure to not make a large memory pressure for >
PAGE_SZErequests (__GFP_NORETRY) and also to not warn about allocation failures. This also rules out the OOM killer as the vmalloc is a more approapriate fallback than a disruptive user visible action.Signed-off-by Michael Jeanson <[email protected]>---
lttng-events.c| 6 +--wrapper/vmalloc.h| 111 +++++++++++++++++++++++++++++++++++++++++++++++++++++-2 files changed, 112 insertions(+), 5 deletions(-)lttng-events.c +1
-1@@ -132,7 +132,7 @@ struct lttng_session *lttng_session_create(void)int i;mutex_lock (&sessions_mutex); - session =kzalloc (sizeof (struct lttng_session ),GFP_KERNEL ); + session =lttng_kvzalloc (sizeof (struct lttng_session ),GFP_KERNEL );if (!session) goto err;INIT_LIST_HEAD (&session->chan);@@ -163,7 +163,7 @@ struct lttng_session *lttng_session_create(void)
err_free_cache:kfree(metadata_cache);
err_free_session:lttng-events.c +1
-1-kfree (session); +lttng_kvfree (session);err:
mutex_unlock(&sessions_mutex); return NULL;lttng-events.c +1
-1@@ -212,7 +212,7 @@ void lttng_session_destroy(struct lttng_session *session)kref_put (&session->metadata_cache->refcount, metadata_cache_destroy);list_del (&session->list);mutex_unlock (&sessions_mutex); -kfree (session); +lttng_kvfree (session); }int lttng_session_statedump (struct lttng_session *session)wrapper/vmalloc.h +3
-2@@ -25,6 +25,9 @@* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA */ +#include <linux/version.h> +#include <linux/vmalloc.h> +#ifdef CONFIG_KALLSYMS #include <linux/kallsyms.h> @@ -51,8 +54,6 @@ void wrapper_vmalloc_sync_all(void) }#else -#include <linux/vmalloc.h> -static inline
voidwrapper_vmalloc_sync_all(void)
{wrapper/vmalloc.h +46
-0@@ -60,4 +61,110 @@ void wrapper_vmalloc_sync_all(void) }#endif +#if (LINUX_VERSION_CODE >=KERNEL_VERSION (4 ,12 ,0 )) +static inline +void *lttng_kvmalloc (unsigned long size,int flags) +{ +void *ret; + + ret =kvmalloc (size, flags); +if (is_vmalloc_addr (ret)) { +/* +* Make sure we don't trigger recursive page faults in the +* tracing fast path. +*/ +wrapper_vmalloc_sync_all (); + } +return ret; +} + +static inline +void *lttng_kvzalloc (unsigned long size,int flags) +{ +void *ret; + + ret =kvzalloc (size, flags); +if (is_vmalloc_addr (ret)) { +/* +* Make sure we don't trigger recursive page faults in the +* tracing fast path. +*/ +wrapper_vmalloc_sync_all (); + } +return ret; +} + +static inline +void lttng_kvfree (const void *addr) +{ +kvfree (addr); +} + +#else + +#include <linux/slab.h> +#include <linux/mm.h> + +/** +* lttng_kvmalloc_node - attempt to allocate physically contiguous memory, but upon
+ * failure, fall back to non-contiguous (vmalloc) allocation.
+ * @size: size of the request.
+ * @flags: gfp mask for the allocation - must be compatible withGFP_KERNEL.
+ *
+ * Uses kmalloc to get the memory but if the allocation fails then falls back
+ * to the vmalloc allocator. Uselttng_kvfreeto free the memory.
+ *
+ * Reclaim modifiers -__GFP_NORETRY,__GFP_REPEATand__GFP_NOFAILare not supported
+ */wrapper/vmalloc.h +51
-0+static inline +void *lttng_kvmalloc (unsigned long size,int flags) +{ +void *ret; + +/* +* vmalloc uses GFP_KERNEL for some internal allocations (e.g page tables) +* so the given set of flags has to be compatible. +*/ +WARN_ON_ONCE ((flags &GFP_KERNEL ) !=GFP_KERNEL ); + +/* +* If the allocation fits in a single page, do not fallback. +*/ +if (size <=PAGE_SIZE ) { +return kmalloc (size, flags); + } + +/* +* Make sure that larger requests are not too disruptive - no OOM +* killer and no allocation failure warnings as we have a fallback +*/ + ret =kmalloc (size, flags | __GFP_NOWARN | __GFP_NORETRY); +if (!ret) { + ret =__vmalloc (size, flags | __GFP_HIGHMEM,PAGE_KERNEL ); +/* +* Make sure we don't trigger recursive page faults in the +* tracing fast path. +*/ +wrapper_vmalloc_sync_all (); + } +return ret; +} + +static inline +void *lttng_kvzalloc (unsigned long size,int flags) +{ +return lttng_kvmalloc (size, flags | __GFP_ZERO); +} + +static inline +void lttng_kvfree (const void *addr) +{ +if (is_vmalloc_addr (addr)) { +vfree (addr); + }else { +kfree (addr); + } +} +#endif +#endif /*
_LTTNG_WRAPPER_VMALLOC_H*/
--
2.7.4
Signature · 7 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Mathieu Desnoyers
Quoted 5 lines · ----- On Sep 21, 2017, at 2:29 PM, Michael Jeanson [email protected] wrote:
This patch is based on the kvmalloc helpers introduced in kernel 4.12.
It will gracefully failover memory allocations of more than one page to vmalloc for systems under high memory pressure or fragmentation.
Quoted 7 lines
Quoted 4 lines
I only used it in
lttng-events.cas a POC, most allocations fit into a single page so I'm not sure how useful this actually is.Thoughts?
Just update the changelog to specify why we need this for struct
lttng_session(~32kB), and you can submit it for good with a "Fix: " tag.
I'm not sure it should be a fix, for this to be of any use all the other allocations bigger than PAGE_SIZE should also use it. Otherwise, the session allocation will succeed but the next sizeable allocation will still fail.
Quoted 4 lines
Thanks,
Mathieu
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 13 lines · ----- On Sep 21, 2017, at 2:43 PM, Michael Jeanson [email protected] wrote:
Quoted 12 lines · Mathieu Desnoyers
Quoted 9 lines · ----- On Sep 21, 2017, at 2:29 PM, Michael Jeanson [email protected] wrote:
This patch is based on the kvmalloc helpers introduced in kernel 4.12.
It will gracefully failover memory allocations of more than one page to vmalloc for systems under high memory pressure or fragmentation.
I only used it in
lttng-events.cas a POC, most allocations fit into a single page so I'm not sure how useful this actually is.Thoughts?
Quoted 7 lines
Quoted 2 lines
Just update the changelog to specify why we need this for struct
lttng_session(~32kB), and you can submit it for good with a "Fix: " tag.I'm not sure it should be a fix, for this to be of any use all the other allocations bigger than
PAGE_SIZEshould also use it. Otherwise, the session allocation will succeed but the next sizeable allocation will still fail.
What other allocations larger than PAGE_SIZE using kmalloc did you spot ?
Thanks,
Mathieu
Quoted 5 lines
Quoted 5 lines
Thanks,
Mathieu
Signature · 7 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 18 lines · Mathieu Desnoyers
Quoted 16 lines · ----- On Sep 21, 2017, at 2:43 PM, Michael Jeanson [email protected] wrote:
Quoted 14 lines · Mathieu Desnoyers
Quoted 9 lines · ----- On Sep 21, 2017, at 2:29 PM, Michael Jeanson [email protected] wrote:
This patch is based on the kvmalloc helpers introduced in kernel 4.12.
It will gracefully failover memory allocations of more than one page to vmalloc for systems under high memory pressure or fragmentation.
I only used it in
lttng-events.cas a POC, most allocations fit into a single page so I'm not sure how useful this actually is.Thoughts?
Just update the changelog to specify why we need this for struct
lttng_session(~32kB), and you can submit it for good with a "Fix: " tag.
Quoted 6 lines
Quoted 4 lines
I'm not sure it should be a fix, for this to be of any use all the other allocations bigger than
PAGE_SIZEshould also use it. Otherwise, the session allocation will succeed but the next sizeable allocation will still fail.What other allocations larger than
PAGE_SIZEusing kmalloc did you spot ?
This is not an exhaustive list :
lttng-context.c:
- new_fields: 136 * n
lttng-context-perf-counters.c:
- events: if you have more than 512 CPUs
lib/prio_heap/lttng_prio_heap.c:
- new_ptrs
But mostly in the ringbuffer, thought I have no idea if a failover to vmalloc is acceptable in this case.
Quoted 12 lines
Thanks,
Mathieu
Quoted 5 lines
Quoted 5 lines
Thanks,
Mathieu
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 34 lines · ----- On Sep 21, 2017, at 4:30 PM, Michael Jeanson [email protected] wrote:
Quoted 18 lines · Mathieu Desnoyers
Quoted 16 lines · ----- On Sep 21, 2017, at 2:43 PM, Michael Jeanson [email protected] wrote:
Quoted 14 lines · Mathieu Desnoyers
Quoted 9 lines · ----- On Sep 21, 2017, at 2:29 PM, Michael Jeanson [email protected] wrote:
This patch is based on the kvmalloc helpers introduced in kernel 4.12.
It will gracefully failover memory allocations of more than one page to vmalloc for systems under high memory pressure or fragmentation.
I only used it in
lttng-events.cas a POC, most allocations fit into a single page so I'm not sure how useful this actually is.Thoughts?
Just update the changelog to specify why we need this for struct
lttng_session(~32kB), and you can submit it for good with a "Fix: " tag.Quoted 6 lines
Quoted 4 lines
I'm not sure it should be a fix, for this to be of any use all the other allocations bigger than
PAGE_SIZEshould also use it. Otherwise, the session allocation will succeed but the next sizeable allocation will still fail.What other allocations larger than
PAGE_SIZEusing kmalloc did you spot ?This is not an exhaustive list :
lttng-context.c:
-new_fields: 136 * n
lttng-context-perf-counters.c:
- events: if you have more than 512 CPUs
Quoted 6 lines
lib/prio_heap/lttng_prio_heap.c:
-new_ptrsBut mostly in the ringbuffer, thought I have no idea if a failover to vmalloc is acceptable in this case.
As long as we issue vmalloc_sync_all after vmalloc, yes, it's acceptable.
Please provide a patch that changes all allocations that can be larger than PAGE_SIZE to the new scheme.
Thanks,
Mathieu
Quoted 12 lines
Quoted 12 lines
Thanks,
Mathieu
Quoted 5 lines
Quoted 5 lines
Thanks,
Mathieu
Signature · 7 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev