From: Uladzislau Rezki <urezki@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 03/10] mm: remove __vfree_deferred
Date: Thu, 19 Jan 2023 19:47:28 +0100 [thread overview]
Message-ID: <Y8mQQHwx4yhdB1oj@pc636> (raw)
In-Reply-To: <20230119100226.789506-4-hch@lst.de>
On Thu, Jan 19, 2023 at 11:02:19AM +0100, Christoph Hellwig wrote:
> Fold __vfree_deferred into vfree_atomic, and call vfree_atomic early on
> from vfree if called from interrupt context so that the extra low-level
> helper can be avoided.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> mm/vmalloc.c | 43 +++++++++++++++++--------------------------
> 1 file changed, 17 insertions(+), 26 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index b989828b45109a..fafb6227f4428f 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2769,20 +2769,6 @@ static void __vunmap(const void *addr, int deallocate_pages)
> kfree(area);
> }
>
> -static inline void __vfree_deferred(const void *addr)
> -{
> - /*
> - * Use raw_cpu_ptr() because this can be called from preemptible
> - * context. Preemption is absolutely fine here, because the llist_add()
> - * implementation is lockless, so it works even if we are adding to
> - * another cpu's list. schedule_work() should be fine with this too.
> - */
> - struct vfree_deferred *p = raw_cpu_ptr(&vfree_deferred);
> -
> - if (llist_add((struct llist_node *)addr, &p->list))
> - schedule_work(&p->wq);
> -}
> -
> /**
> * vfree_atomic - release memory allocated by vmalloc()
> * @addr: memory base address
> @@ -2792,13 +2778,19 @@ static inline void __vfree_deferred(const void *addr)
> */
> void vfree_atomic(const void *addr)
> {
> - BUG_ON(in_nmi());
> + struct vfree_deferred *p = raw_cpu_ptr(&vfree_deferred);
>
> + BUG_ON(in_nmi());
> kmemleak_free(addr);
>
> - if (!addr)
> - return;
> - __vfree_deferred(addr);
> + /*
> + * Use raw_cpu_ptr() because this can be called from preemptible
> + * context. Preemption is absolutely fine here, because the llist_add()
> + * implementation is lockless, so it works even if we are adding to
> + * another cpu's list. schedule_work() should be fine with this too.
> + */
> + if (addr && llist_add((struct llist_node *)addr, &p->list))
> + schedule_work(&p->wq);
> }
>
> /**
> @@ -2820,17 +2812,16 @@ void vfree_atomic(const void *addr)
> */
> void vfree(const void *addr)
> {
> - BUG_ON(in_nmi());
> + if (unlikely(in_interrupt())) {
> + vfree_atomic(addr);
> + return;
> + }
>
> + BUG_ON(in_nmi());
> kmemleak_free(addr);
> + might_sleep();
>
> - might_sleep_if(!in_interrupt());
> -
> - if (!addr)
> - return;
> - if (unlikely(in_interrupt()))
> - __vfree_deferred(addr);
> - else
> + if (addr)
> __vunmap(addr, 1);
> }
> EXPORT_SYMBOL(vfree);
> --
> 2.39.0
>
Such folding makes sense to me.
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Uladzislau Rezki
next prev parent reply other threads:[~2023-01-19 18:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 10:02 cleanup vfree and vunmap Christoph Hellwig
2023-01-19 10:02 ` [PATCH 01/10] vmalloc: reject vmap with VM_FLUSH_RESET_PERMS Christoph Hellwig
2023-01-19 18:46 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 02/10] mm: remove __vfree Christoph Hellwig
2023-01-19 18:47 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 03/10] mm: remove __vfree_deferred Christoph Hellwig
2023-01-19 18:47 ` Uladzislau Rezki [this message]
2023-01-19 10:02 ` [PATCH 04/10] mm: move vmalloc_init and free_work down in vmalloc.c Christoph Hellwig
2023-01-19 18:48 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 05/10] mm: call vfree instead of __vunmap from delayed_vfree_work Christoph Hellwig
2023-01-19 18:48 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 06/10] mm: move __remove_vm_area out of va_remove_mappings Christoph Hellwig
2023-01-19 18:48 ` Uladzislau Rezki
2023-01-20 7:41 ` Christoph Hellwig
2023-01-20 11:32 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 07/10] mm: use remove_vm_area in __vunmap Christoph Hellwig
2023-01-19 18:49 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 08/10] mm: move debug checks from __vunmap to remove_vm_area Christoph Hellwig
2023-01-19 18:49 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 09/10] mm: split __vunmap Christoph Hellwig
2023-01-19 18:50 ` Uladzislau Rezki
2023-01-20 7:42 ` Christoph Hellwig
2023-01-20 11:32 ` Uladzislau Rezki
2023-01-19 10:02 ` [PATCH 10/10] mm: refactor va_remove_mappings Christoph Hellwig
2023-01-19 18:50 ` Uladzislau Rezki
2023-01-19 16:45 ` cleanup vfree and vunmap Uladzislau Rezki
2023-01-21 7:10 Christoph Hellwig
2023-01-21 7:10 ` [PATCH 03/10] mm: remove __vfree_deferred Christoph Hellwig
2023-01-23 10:37 ` David Hildenbrand
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=Y8mQQHwx4yhdB1oj@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
/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