From: Uladzislau Rezki <urezki@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Uladzislau Rezki <urezki@gmail.com>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Baoquan He <bhe@redhat.com>
Subject: Re: [patch 0/6] mm/vmalloc: Assorted fixes and improvements
Date: Tue, 23 May 2023 18:24:16 +0200 [thread overview]
Message-ID: <ZGzosGgKTO5RRqMj@pc636> (raw)
In-Reply-To: <20230523135902.517032811@linutronix.de>
On Tue, May 23, 2023 at 04:02:09PM +0200, Thomas Gleixner wrote:
> Following up to the discussion about excessive TLB flushes
>
> https://lore.kernel.org/all/87a5y5a6kj.ffs@tglx
>
> this series addresses the following issues:
>
>
> 1) Prevent the stale TLB problem related to fully utilized vmap blocks
>
>
> 2) Avoid the double per CPU list walk in _vm_unmap_aliases()
>
>
> 3) Avoid flushing dirty space over and over
>
>
> 4) Add a lockless quickcheck in vb_alloc() and add missing
> READ/WRITE_ONCE() annotations
>
> 5) Prevent overeager purging of usable vmap_blocks if
> not under memory/address space pressure.
>
> Thanks,
>
> tglx
Thank you for fixing it!
<snip>
urezki@pc638:~/data/raid0/coding/linux.git$ make -j64 bzImage
DESCEND objtool
INSTALL libsubcmd_headers
CALL scripts/checksyscalls.sh
CC mm/vmalloc.o
In file included from ./include/linux/list_lru.h:14,
from ./include/linux/fs.h:13,
from ./include/linux/huge_mm.h:8,
from ./include/linux/mm.h:855,
from mm/vmalloc.c:12:
mm/vmalloc.c: In function ‘_vm_unmap_aliases’:
mm/vmalloc.c:2220:19: error: ‘struct vmap_block_queue’ has no member named ‘vmap_blocks’
2220 | xa_for_each(&vbq->vmap_blocks, idx, vb) {
| ^~
./include/linux/xarray.h:449:23: note: in definition of macro ‘xa_for_each_range’
449 | entry = xa_find(xa, &index, last, XA_PRESENT); \
| ^~
./include/linux/xarray.h:501:2: note: in expansion of macro ‘xa_for_each_start’
501 | xa_for_each_start(xa, index, entry, 0)
| ^~~~~~~~~~~~~~~~~
mm/vmalloc.c:2220:3: note: in expansion of macro ‘xa_for_each’
2220 | xa_for_each(&vbq->vmap_blocks, idx, vb) {
| ^~~~~~~~~~~
mm/vmalloc.c:2220:19: error: ‘struct vmap_block_queue’ has no member named ‘vmap_blocks’
2220 | xa_for_each(&vbq->vmap_blocks, idx, vb) {
| ^~
./include/linux/xarray.h:451:29: note: in definition of macro ‘xa_for_each_range’
451 | entry = xa_find_after(xa, &index, last, XA_PRESENT))
| ^~
./include/linux/xarray.h:501:2: note: in expansion of macro ‘xa_for_each_start’
501 | xa_for_each_start(xa, index, entry, 0)
| ^~~~~~~~~~~~~~~~~
mm/vmalloc.c:2220:3: note: in expansion of macro ‘xa_for_each’
2220 | xa_for_each(&vbq->vmap_blocks, idx, vb) {
| ^~~~~~~~~~~
mm/vmalloc.c:2228:9: error: too few arguments to function ‘purge_fragmented_block’
2228 | if (!purge_fragmented_block(vb, vbq, &purge_list) &&
| ^~~~~~~~~~~~~~~~~~~~~~
mm/vmalloc.c:2047:13: note: declared here
2047 | static bool purge_fragmented_block(struct vmap_block *vb, struct vmap_block_queue *vbq,
| ^~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:252: mm/vmalloc.o] Error 1
make[1]: *** [scripts/Makefile.build:494: mm] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:2025: .] Error 2
urezki@pc638:~/data/raid0/coding/linux.git$ ^C
<snip>
Could please fix it? :)
--
Uladzislau Rezki
next prev parent reply other threads:[~2023-05-23 16:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 14:02 [patch 0/6] mm/vmalloc: Assorted fixes and improvements Thomas Gleixner
2023-05-23 14:02 ` [patch 1/6] mm/vmalloc: Prevent stale TLBs in fully utilized blocks Thomas Gleixner
2023-05-23 15:17 ` Christoph Hellwig
2023-05-23 16:40 ` Thomas Gleixner
2023-05-23 16:47 ` Uladzislau Rezki
2023-05-23 19:18 ` Lorenzo Stoakes
2023-05-24 9:19 ` Uladzislau Rezki
2023-05-24 9:25 ` Baoquan He
2023-05-24 9:51 ` Thomas Gleixner
2023-05-24 11:24 ` Baoquan He
2023-05-24 11:26 ` Baoquan He
2023-05-24 11:36 ` Uladzislau Rezki
2023-05-24 12:49 ` Thomas Gleixner
2023-05-24 12:44 ` Thomas Gleixner
2023-05-24 13:41 ` Baoquan He
2023-05-24 14:31 ` Thomas Gleixner
2023-05-24 9:32 ` Baoquan He
2023-05-24 9:52 ` Thomas Gleixner
2023-05-24 14:10 ` Baoquan He
2023-05-24 14:35 ` Thomas Gleixner
2023-05-23 14:02 ` [patch 2/6] mm/vmalloc: Avoid iterating over per CPU vmap blocks twice Thomas Gleixner
2023-05-23 15:21 ` Christoph Hellwig
2023-05-23 14:02 ` [patch 3/6] mm/vmalloc: Prevent flushing dirty space over and over Thomas Gleixner
2023-05-23 15:27 ` Christoph Hellwig
2023-05-23 16:10 ` Thomas Gleixner
2023-05-24 9:43 ` Baoquan He
2023-05-23 14:02 ` [patch 4/6] mm/vmalloc: Check free space in vmap_block lockless Thomas Gleixner
2023-05-23 15:29 ` Christoph Hellwig
2023-05-23 16:17 ` Thomas Gleixner
2023-05-24 9:20 ` Uladzislau Rezki
2023-05-23 14:02 ` [patch 5/6] mm/vmalloc: Add missing READ/WRITE_ONCE() annotations Thomas Gleixner
2023-05-24 9:15 ` Uladzislau Rezki
2023-05-23 14:02 ` [patch 6/6] mm/vmalloc: Dont purge usable blocks unnecessarily Thomas Gleixner
2023-05-23 15:30 ` Christoph Hellwig
2023-05-24 10:34 ` Baoquan He
2023-05-24 12:55 ` Thomas Gleixner
2023-05-23 16:24 ` Uladzislau Rezki [this message]
2023-05-23 17:33 ` [patch 0/6] mm/vmalloc: Assorted fixes and improvements Thomas Gleixner
2023-05-23 17:39 ` Thomas Gleixner
2023-05-23 17:48 ` Uladzislau Rezki
2023-05-23 17:51 ` Uladzislau Rezki
2023-05-23 17:55 ` Uladzislau Rezki
2023-05-23 18:40 ` Thomas Gleixner
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=ZGzosGgKTO5RRqMj@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.