From: Matthew Wilcox <willy@infradead.org>
To: Roman Gushchin <guroan@gmail.com>
Cc: linux-mm@kvack.org, Alexey Dobriyan <adobriyan@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Roman Gushchin <guro@fb.com>
Subject: Re: [RFC 2/4] mm: separate memory allocation and actual work in alloc_vmap_area()
Date: Fri, 14 Dec 2018 10:13:22 -0800 [thread overview]
Message-ID: <20181214181322.GC10600@bombadil.infradead.org> (raw)
In-Reply-To: <20181214180720.32040-3-guro@fb.com>
On Fri, Dec 14, 2018 at 10:07:18AM -0800, Roman Gushchin wrote:
> alloc_vmap_area() is allocating memory for the vmap_area, and
> performing the actual lookup of the vm area and vmap_area
> initialization.
>
> This prevents us from using a pre-allocated memory for the map_area
> structure, which can be used in some cases to minimize the number
> of required memory allocations.
>
> Let's keep the memory allocation part in alloc_vmap_area() and
> separate everything else into init_vmap_area().
Oh good, I was considering doing something like this eventually.
> +++ b/mm/vmalloc.c
> @@ -395,16 +395,11 @@ static void purge_vmap_area_lazy(void);
>
> static BLOCKING_NOTIFIER_HEAD(vmap_notify_list);
>
> -/*
> - * Allocate a region of KVA of the specified size and alignment, within the
> - * vstart and vend.
> - */
> -static struct vmap_area *alloc_vmap_area(unsigned long size,
> - unsigned long align,
> - unsigned long vstart, unsigned long vend,
> - int node, gfp_t gfp_mask)
> +static int init_vmap_area(struct vmap_area *va, unsigned long size,
> + unsigned long align, unsigned long vstart,
> + unsigned long vend, int node, gfp_t gfp_mask)
> {
> - struct vmap_area *va;
> +
Why the blank line?
> struct rb_node *n;
> unsigned long addr;
> int purged = 0;
> @@ -416,11 +411,6 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
>
> might_sleep();
>
> - va = kmalloc_node(sizeof(struct vmap_area),
> - gfp_mask & GFP_RECLAIM_MASK, node);
> - if (unlikely(!va))
> - return ERR_PTR(-ENOMEM);
> -
> /*
> * Only scan the relevant parts containing pointers to other objects
> * to avoid false negatives.
> @@ -512,7 +502,7 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
> BUG_ON(va->va_start < vstart);
> BUG_ON(va->va_end > vend);
>
> - return va;
> + return 0;
>
> overflow:
> spin_unlock(&vmap_area_lock);
> @@ -534,10 +524,38 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
> if (!(gfp_mask & __GFP_NOWARN) && printk_ratelimit())
> pr_warn("vmap allocation for size %lu failed: use vmalloc=<size> to increase size\n",
> size);
> - kfree(va);
> - return ERR_PTR(-EBUSY);
> +
> + return -EBUSY;
> +}
> +
> +/*
> + * Allocate a region of KVA of the specified size and alignment, within the
> + * vstart and vend.
> + */
> +static struct vmap_area *alloc_vmap_area(unsigned long size,
> + unsigned long align,
> + unsigned long vstart,
> + unsigned long vend,
> + int node, gfp_t gfp_mask)
> +{
> + struct vmap_area *va;
> + int ret;
> +
> + va = kmalloc_node(sizeof(struct vmap_area),
> + gfp_mask & GFP_RECLAIM_MASK, node);
> + if (unlikely(!va))
> + return ERR_PTR(-ENOMEM);
> +
> + ret = init_vmap_area(va, size, align, vstart, vend, node, gfp_mask);
> + if (ret) {
> + kfree(va);
> + return ERR_PTR(ret);
> + }
> +
> + return va;
> }
>
> +
Another spurious blank line?
With these two fixed,
Reviewed-by: Matthew Wilcox <willy@infradead.org>
next prev parent reply other threads:[~2018-12-14 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 18:07 [RFC 0/4] vmalloc enhancements Roman Gushchin
2018-12-14 18:07 ` [RFC 1/4] mm: refactor __vunmap() to avoid duplicated call to find_vm_area() Roman Gushchin
2018-12-14 18:24 ` Matthew Wilcox
2018-12-14 18:07 ` [RFC 2/4] mm: separate memory allocation and actual work in alloc_vmap_area() Roman Gushchin
2018-12-14 18:13 ` Matthew Wilcox [this message]
2018-12-14 19:40 ` Joe Perches
2018-12-14 19:45 ` Matthew Wilcox
2018-12-14 21:57 ` Roman Gushchin
2018-12-15 2:22 ` Joe Perches
2018-12-14 18:07 ` [RFC 3/4] mm: allocate vmalloc metadata in one allocation Roman Gushchin
2018-12-14 18:07 ` [RFC 4/4] mm: show number of vmalloc pages in /proc/meminfo Roman Gushchin
2018-12-14 18:29 ` Matthew Wilcox
2018-12-14 18:42 ` Roman Gushchin
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=20181214181322.GC10600@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=adobriyan@gmail.com \
--cc=guro@fb.com \
--cc=guroan@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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