public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: Dexuan Cui <decui@microsoft.com>
Cc: Saurabh Singh Sengar <ssengar@linux.microsoft.com>,
	Nuno Das Neves <nunodasneves@linux.microsoft.com>,
	KY Srinivasan <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"wei.liu@kernel.org" <wei.liu@kernel.org>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Saurabh Singh Sengar <ssengar@microsoft.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks
Date: Fri, 26 Jul 2024 06:34:53 +0000	[thread overview]
Message-ID: <ZqNDjUALdN2Qtop6@csail.mit.edu> (raw)
In-Reply-To: <SA1PR21MB1317797B68A7AFCD8D75650ABFB42@SA1PR21MB1317.namprd21.prod.outlook.com>

On Fri, Jul 26, 2024 at 12:01:33AM +0000, Dexuan Cui wrote:
> > From: Saurabh Singh Sengar <ssengar@linux.microsoft.com>
> > Sent: Thursday, July 25, 2024 8:35 AM
> > Subject: Re: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks
> 
> Without the patch, I think the current CPU uses IPIs to let the other
> CPUs, one by one,  run the function calls, and synchronously waits
> for the function calls to finish.
> 
> IMO the patch is not "Deferring per cpu tasks". "Defer" means "let it
> happen later". Here it schedules work items to different CPUs, and
> the work items immediately start to run on these CPUs.
> 
> I would suggest a more accurate subject:
> Drivers: hv: vmbus: Run hv_synic_init() concurrently
> 

It would be great to call out the "why" as well in the title,
something like:

Drivers: hv: vmbus: Speed-up booting by running hv_synic_init() concurrently

Regards,
Srivatsa
Microsoft Linux Systems Group

  parent reply	other threads:[~2024-07-26  6:35 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
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 [this message]
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=ZqNDjUALdN2Qtop6@csail.mit.edu \
    --to=srivatsa@csail.mit.edu \
    --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=nunodasneves@linux.microsoft.com \
    --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