linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Baoquan He <bhe@redhat.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
	linux-mm@kvack.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] mm/vmalloc.c: optimize code in decay_va_pool_node() a little bit
Date: Thu, 17 Apr 2025 18:18:57 +0200	[thread overview]
Message-ID: <aAEp8R0GcKCXtMwG@pc636> (raw)
In-Reply-To: <aABswErLwX7o7OXa@MiWiFi-R3L-srv>

On Thu, Apr 17, 2025 at 10:51:44AM +0800, Baoquan He wrote:
> On 04/16/25 at 03:50pm, Uladzislau Rezki wrote:
> > On Tue, Apr 15, 2025 at 10:39:50AM +0800, Baoquan He wrote:
> > > When purge lazily freed vmap areas, VA stored in vn->pool[] will also be
> > > taken away into free vmap tree partially or completely accordingly, that
> > > is done in decay_va_pool_node(). When doing that, for each pool of node,
> > > the whole list is detached from the pool for handling. At this time,
> > > that pool is empty. It's not necessary to update the pool size each time
> > > when one VA is removed and addded into free vmap tree.
> > > 
> > > Here change code to update the pool size when attaching the pool back.
> > > 
> > > Signed-off-by: Baoquan He <bhe@redhat.com>
> > > ---
> > >  mm/vmalloc.c | 23 +++++++++++------------
> > >  1 file changed, 11 insertions(+), 12 deletions(-)
> > > 
> > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > > index 488d69b56765..bf735c890878 100644
> > > --- a/mm/vmalloc.c
> > > +++ b/mm/vmalloc.c
> > > @@ -2150,7 +2150,7 @@ decay_va_pool_node(struct vmap_node *vn, bool full_decay)
> > >  	LIST_HEAD(decay_list);
> > >  	struct rb_root decay_root = RB_ROOT;
> > >  	struct vmap_area *va, *nva;
> > > -	unsigned long n_decay;
> > > +	unsigned long n_decay, len;
> > >  	int i;
> > >  
> > >  	for (i = 0; i < MAX_VA_SIZE_PAGES; i++) {
> > > @@ -2164,22 +2164,20 @@ decay_va_pool_node(struct vmap_node *vn, bool full_decay)
> > >  		list_replace_init(&vn->pool[i].head, &tmp_list);
> > >  		spin_unlock(&vn->pool_lock);
> > >  
> > > -		if (full_decay)
> > > -			WRITE_ONCE(vn->pool[i].len, 0);
> > > +		len = n_decay = vn->pool[i].len;
> > > +		WRITE_ONCE(vn->pool[i].len, 0);
> > >  
> > >  		/* Decay a pool by ~25% out of left objects. */
> > > -		n_decay = vn->pool[i].len >> 2;
> > > +		if (!full_decay)
> > > +			n_decay >>= 2;
> > > +		len -= n_decay;
> > >  
> > >  		list_for_each_entry_safe(va, nva, &tmp_list, list) {
> > > +			if (!n_decay)
> > > +				break;
> > >  			list_del_init(&va->list);
> > >  			merge_or_add_vmap_area(va, &decay_root, &decay_list);
> > > -
> > > -			if (!full_decay) {
> > > -				WRITE_ONCE(vn->pool[i].len, vn->pool[i].len - 1);
> > > -
> > > -				if (!--n_decay)
> > > -					break;
> > > -			}
> > > +			n_decay--;
> > >  		}
> > >  
> > >  		/*
> > > @@ -2188,9 +2186,10 @@ decay_va_pool_node(struct vmap_node *vn, bool full_decay)
> > >  		 * can populate the pool therefore a simple list replace
> > >  		 * operation takes place here.
> > >  		 */
> > > -		if (!full_decay && !list_empty(&tmp_list)) {
> > > +		if (!list_empty(&tmp_list)) {
> > >  			spin_lock(&vn->pool_lock);
> > >  			list_replace_init(&tmp_list, &vn->pool[i].head);
> > > +			vn->pool[i].len = len;
> > >  			spin_unlock(&vn->pool_lock);
> > >  		}
> > >  	}
> > > -- 
> > > 2.41.0
> > > 
> > Which Linux version this patch is based on? I can not apply it.
> 
> I can apply them on the latest mainline kernel, next/master and
> mm-new branch of akpm/mm.git. I checked just now.
> 
Sounds good.

--
Uladzislau Rezki


  reply	other threads:[~2025-04-17 16:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  2:39 [PATCH 0/5] mm/vmalloc.c: code cleanup and improvements Baoquan He
2025-04-15  2:39 ` [PATCH 1/5] mm/vmalloc.c: change purge_ndoes as local static variable Baoquan He
2025-04-15 10:47   ` Uladzislau Rezki
2025-04-15 19:08   ` Shivank Garg
2025-04-15 23:53   ` Vishal Moola (Oracle)
2025-04-15  2:39 ` [PATCH 2/5] mm/vmalloc.c: find the vmap of vmap_nodes in reverse order Baoquan He
2025-04-15 15:25   ` Uladzislau Rezki
2025-04-15 23:41     ` Baoquan He
2025-04-15 19:09   ` Shivank Garg
2025-04-15  2:39 ` [PATCH 3/5] mm/vmalloc.c: optimize code in decay_va_pool_node() a little bit Baoquan He
2025-04-15 10:29   ` Shivank Garg
2025-04-15 14:05     ` Baoquan He
2025-04-15 19:02       ` Shivank Garg
2025-04-16 13:50   ` Uladzislau Rezki
2025-04-17  2:51     ` Baoquan He
2025-04-17 16:18       ` Uladzislau Rezki [this message]
2025-04-15  2:39 ` [PATCH 4/5] mm/vmalloc: optimize function vm_unmap_aliases() Baoquan He
2025-04-15 10:44   ` Uladzislau Rezki
2025-04-15 19:10   ` Shivank Garg
2025-04-15 23:54   ` Vishal Moola (Oracle)
2025-04-15  2:39 ` [PATCH 5/5] mm/vmalloc.c: return explicit error value in alloc_vmap_area() Baoquan He
2025-04-15  6:44   ` Baoquan He
2025-04-15  7:22   ` Shivank Garg
2025-04-15 13:01     ` Baoquan He
2025-04-15 19:00       ` Shivank Garg
2025-04-15 22:57         ` Baoquan He
2025-04-16 14:28   ` Uladzislau Rezki
2025-04-17  3:02     ` Baoquan He
2025-04-17 16:17       ` Uladzislau Rezki
2025-04-15 15:29 ` [PATCH 0/5] mm/vmalloc.c: code cleanup and improvements Uladzislau Rezki
2025-04-15 22:55   ` Baoquan He
2025-04-15 19:06 ` Shivank Garg

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=aAEp8R0GcKCXtMwG@pc636 \
    --to=urezki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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