[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xen cpu scheduler internals

  • To: "Xen-devel@xxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxx>
  • From: tutu sky <ooohooo_u@xxxxxxxxxxx>
  • Date: Mon, 18 Apr 2016 08:04:49 +0000
  • Accept-language: en-US
  • Delivery-date: Mon, 18 Apr 2016 08:05:10 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHRmNQdO2r37aH5l0a922diEsj+v5+PX/iq
  • Thread-topic: xen cpu scheduler internals

Hi, I think pick_cpu function in schedule.c can be a good starting point, am i 

From: tutu sky <ooohooo_u@xxxxxxxxxxx>
Sent: Sunday, April 17, 2016 6:18 PM
To: Xen-devel@xxxxxxxxxxxxx
Subject: xen cpu scheduler internals

I know that scheduling is done via two main functions and their effective 
one 'schedule()' in schedule.c and another 'do_schedule(...)', which is 
specific for every scheduling policy.
my question is that (although it may seem clear and very common for kernel 
developers, but not as mush for me):
when a vcpu is selected to run on a specific cpu, what is the policy for 
choosing cpu (pcpu)?
I see smp_processor_id() very frequent, and in my suppose, the current cpu is 
the cpu which is used for scheduling (i just think so).

if i need to choose and find more than one cpu for running my tasks on, what 
should i do in scheduler context?

Thanks and regards.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.