linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: linux-mm@kvack.org, Xu Yu <xuyu@linux.alibaba.com>
Cc: akpm@linux-foundation.org
Subject: Re: [PATCH] mm/vmalloc: allocate small pages for area->pages
Date: Thu, 09 Dec 2021 18:23:25 +1000	[thread overview]
Message-ID: <1639037882.ddpnbp5ftw.astroid@bobo.none> (raw)
In-Reply-To: <dd04f516643fde4206c1fe93818526a768125c75.1638870169.git.xuyu@linux.alibaba.com>

Excerpts from Xu Yu's message of December 7, 2021 7:46 pm:
> The area->pages stores the struct pages allocated for vmalloc mappings.
> The allocated memory can be hugepage if arch has HAVE_ARCH_HUGE_VMALLOC
> set, while area->pages itself does not have to be hugepage backed.
> 
> Suppose that we want to vmalloc 1026M of memory, then area->pages is
> 2052K in size, which is large than PMD_SIZE when the pagesize is 4K.
> Currently, 4096K will be allocated for area->pages, wherein 2044K is
> wasted.
> 
> This introduces __vmalloc_node_no_huge, and makes area->pages backed by
> small pages, because I think to allocate hugepage for area->pages is
> unnecessary and vulnerable to abuse.

Any vmalloc allocation will be subject to internal fragmentation like
this. What makes this one special? Is there a way to improve it for
all with some heuristic?

There would be an argument for a size-optimised vmalloc vs a space 
optimised one. An accounting strucutre like this doesn't matter
much for speed. A vfs hash table does. Is it worth doing though? How
much do you gain in practice?

Thanks,
Nick

> 
> Signed-off-by: Xu Yu <xuyu@linux.alibaba.com>
> ---
>  include/linux/vmalloc.h |  2 ++
>  mm/vmalloc.c            | 15 ++++++++++++---
>  2 files changed, 14 insertions(+), 3 deletions(-)
> 
> diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
> index 6e022cc712e6..e93f39eb46a5 100644
> --- a/include/linux/vmalloc.h
> +++ b/include/linux/vmalloc.h
> @@ -150,6 +150,8 @@ extern void *__vmalloc_node_range(unsigned long size, unsigned long align,
>  			const void *caller) __alloc_size(1);
>  void *__vmalloc_node(unsigned long size, unsigned long align, gfp_t gfp_mask,
>  		int node, const void *caller) __alloc_size(1);
> +void *__vmalloc_node_no_huge(unsigned long size, unsigned long align,
> +		gfp_t gfp_mask, int node, const void *caller) __alloc_size(1);
>  void *vmalloc_no_huge(unsigned long size) __alloc_size(1);
>  
>  extern void vfree(const void *addr);
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index d2a00ad4e1dd..0bdbb96d3e3f 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2925,17 +2925,18 @@ static void *__vmalloc_area_node(struct vm_struct *area, gfp_t gfp_mask,
>  	unsigned long size = get_vm_area_size(area);
>  	unsigned long array_size;
>  	unsigned int nr_small_pages = size >> PAGE_SHIFT;
> +	unsigned int max_small_pages = ALIGN(size, 1UL << page_shift) >> PAGE_SHIFT;
>  	unsigned int page_order;
>  
> -	array_size = (unsigned long)nr_small_pages * sizeof(struct page *);
> +	array_size = (unsigned long)max_small_pages * sizeof(struct page *);
>  	gfp_mask |= __GFP_NOWARN;
>  	if (!(gfp_mask & (GFP_DMA | GFP_DMA32)))
>  		gfp_mask |= __GFP_HIGHMEM;
>  
>  	/* Please note that the recursion is strictly bounded. */
>  	if (array_size > PAGE_SIZE) {
> -		area->pages = __vmalloc_node(array_size, 1, nested_gfp, node,
> -					area->caller);
> +		area->pages = __vmalloc_node_no_huge(array_size, 1, nested_gfp,
> +						     node, area->caller);
>  	} else {
>  		area->pages = kmalloc_node(array_size, nested_gfp, node);
>  	}
> @@ -3114,6 +3115,14 @@ void *__vmalloc_node(unsigned long size, unsigned long align,
>  	return __vmalloc_node_range(size, align, VMALLOC_START, VMALLOC_END,
>  				gfp_mask, PAGE_KERNEL, 0, node, caller);
>  }
> +
> +void *__vmalloc_node_no_huge(unsigned long size, unsigned long align,
> +			     gfp_t gfp_mask, int node, const void *caller)
> +{
> +	return __vmalloc_node_range(size, align, VMALLOC_START, VMALLOC_END,
> +				gfp_mask, PAGE_KERNEL, VM_NO_HUGE_VMAP, node, caller);
> +}
> +
>  /*
>   * This is only for performance analysis of vmalloc and stress purpose.
>   * It is required by vmalloc test module, therefore do not use it other
> -- 
> 2.20.1.2432.ga663e714
> 
> 


  reply	other threads:[~2021-12-09  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  9:46 Xu Yu
2021-12-09  8:23 ` Nicholas Piggin [this message]
2021-12-09  9:27   ` Yu Xu
2021-12-09 10:59     ` Nicholas Piggin

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=1639037882.ddpnbp5ftw.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=xuyu@linux.alibaba.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