[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZqNDjUALdN2Qtop6@csail.mit.edu>
Date: Fri, 26 Jul 2024 06:34:53 +0000
From: "Srivatsa S. Bhat" <srivatsa@...il.mit.edu>
To: Dexuan Cui <decui@...rosoft.com>
Cc: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>,
Nuno Das Neves <nunodasneves@...ux.microsoft.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Saurabh Singh Sengar <ssengar@...rosoft.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks
On Fri, Jul 26, 2024 at 12:01:33AM +0000, Dexuan Cui wrote:
> > From: Saurabh Singh Sengar <ssengar@...ux.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
Powered by blists - more mailing lists