All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Yanfei Xu <yanfei.xu@bytedance.com>
Subject: 答复: [????] Re: [PATCH] KVM: irqchip: allocate routing entries in chunks
Date: Thu, 10 Sep 2026 03:26:54 +0000	[thread overview]
Message-ID: <7d6d2449013a4435b71148177820e26d@baidu.com> (raw)
In-Reply-To: <aqH6YcHWk_GmJlqF@google.com>



> Please look at Yanfei's series and help come to an agreement on how best to fix
> this.  I am trying to get to Yanfei's series, and normally would take a close look
> at both, but I am extremely short on cycles at the moment.
> 
> https://lore.kernel.org/all/20260525035242.107264-1-yanfei.xu@bytedance.
> com
> 
Hi Sean,

Thanks for pointing me to Yanfei's series. I agree that both approaches
aim to reduce the allocation overhead in KVM_SET_GSI_ROUTING().

One main concern with using kvalloc() for the entire routing entry array is
that, under severe memory fragmentation, it may fall back to vmalloc().
The vmalloc() path can have relatively high and less predictable overhead,
especially when routing tables are updated frequently when guest OS is
running irqbalance.

Thanks
[Li,Rongqing] 

  reply	other threads:[~2026-09-10  3:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 12:01 [PATCH] KVM: irqchip: allocate routing entries in chunks lirongqing
2026-09-10  0:31 ` Sean Christopherson
2026-09-10  3:26   ` Li,Rongqing [this message]
2026-09-10 14:35     ` 答复: [????] " Yanfei Xu

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=7d6d2449013a4435b71148177820e26d@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=yanfei.xu@bytedance.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 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.