From: Vipin Sharma <vipinsh@google.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Liang Chen <liangchen.linux@gmail.com>,
pbonzini@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, David Matlack <dmatlack@google.com>
Subject: Re: [PATCH] KVM: x86/mmu: Register MMU shrinker only when necessary
Date: Mon, 19 Aug 2024 14:40:14 -0700 [thread overview]
Message-ID: <20240819214014.GA2313467.vipinsh@google.com> (raw)
In-Reply-To: <ZrzCD-cL4N1DsRaO@google.com>
On 2024-08-14 07:41:19, Sean Christopherson wrote:
> +Vipin and David
>
> On Wed, Aug 14, 2024, Liang Chen wrote:
> > The shrinker is allocated with TDP MMU, which is meaningless except for
> > nested VMs, and 'count_objects' is also called each time the reclaim
> > path tries to shrink slab caches. Let's allocate the shrinker only when
> > necessary.
>
> This is definitely not worth the complexity. In its current form, KVM's shrinker
> is quite useless[1], and there were plans to repurpose the shrinker to free pages
> from the so called "mmu caches"[2], i.e. free pages that are guaranteed to not be
> in use.
>
> Vipin/David, what happened to that series? Are we still working on it?
>
> [1] https://lore.kernel.org/lkml/Y45dldZnI6OIf+a5@google.com
> [2] https://lore.kernel.org/all/20221222023457.1764-2-vipinsh@google.com
NUMA aware page table series got deprioritized, so, MMU shrinker changes
also moved to back burner.
I will extract the patch [2] above and send it as a separate series which
just changes the Shrinker behavior as it is independent of NUMA aware
page table effort.
prev parent reply other threads:[~2024-08-19 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 8:23 [PATCH] KVM: x86/mmu: Register MMU shrinker only when necessary Liang Chen
2024-08-14 14:41 ` Sean Christopherson
2024-08-19 21:40 ` Vipin Sharma [this message]
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=20240819214014.GA2313467.vipinsh@google.com \
--to=vipinsh@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=liangchen.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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