Linux-HyperV List
 help / color / mirror / Atom feed
From: Nuno Das Neves <nunodasneves@linux.microsoft.com>
To: Saurabh Sengar <ssengar@linux.microsoft.com>,
	kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, linux-hyperv@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: ssengar@microsoft.com, srivatsa@csail.mit.edu
Subject: Re: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks
Date: Thu, 25 Jul 2024 08:23:21 -0700	[thread overview]
Message-ID: <133be5cb-761e-4646-96ec-b6b53f0c1097@linux.microsoft.com> (raw)
In-Reply-To: <1721885164-6962-1-git-send-email-ssengar@linux.microsoft.com>

On 7/24/2024 10:26 PM, Saurabh Sengar wrote:
> Currently on a very large system with 1780 CPUs, hv_acpi_init takes
> around 3 seconds to complete for all the CPUs. This is because of
> sequential synic initialization for each CPU.
> 
> Defer these tasks so that each CPU executes hv_acpi_init in parallel
> to take full advantage of multiple CPUs.

I think you mean hv_synic_init() here, not hv_acpi_init()?

> 
> This solution saves around 2 seconds of boot time on a 1780 CPU system,
> that around 66% improvement in the existing logic.
> 
> Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
> ---
>  drivers/hv/vmbus_drv.c | 33 ++++++++++++++++++++++++++++++---
>  1 file changed, 30 insertions(+), 3 deletions(-)
> 

LGTM otherwise.

Reviewed-by: Nuno Das Neves <nunodasneves@linux.microsoft.com>


  reply	other threads:[~2024-07-25 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  5:26 [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks Saurabh Sengar
2024-07-25 15:23 ` Nuno Das Neves [this message]
2024-07-25 15:35   ` Saurabh Singh Sengar
2024-07-26  0:01     ` Dexuan Cui
2024-07-26  5:26       ` Saurabh Singh Sengar
2024-07-26  6:02         ` Dexuan Cui
2024-07-26  6:34       ` Srivatsa S. Bhat
2024-07-26 11:26         ` Saurabh Singh Sengar
2024-07-27 12:53           ` Srivatsa S. Bhat
2024-07-28  4:32 ` Michael Kelley
2024-07-28  9:18   ` Saurabh Singh Sengar
2024-07-28 14:06     ` Michael Kelley
2024-07-28 15:40       ` Saurabh Singh Sengar

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=133be5cb-761e-4646-96ec-b6b53f0c1097@linux.microsoft.com \
    --to=nunodasneves@linux.microsoft.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srivatsa@csail.mit.edu \
    --cc=ssengar@linux.microsoft.com \
    --cc=ssengar@microsoft.com \
    --cc=wei.liu@kernel.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