----- Original Message ----- > From: "Gilad Chaplik" <[email protected]> > To: "Chuan Liao (Jason Liao, HPservers-Core-OE-PSC)" <[email protected]> > Cc: [email protected], "arch" <[email protected]>, "vdsm-devel" > <[email protected]> > Sent: Monday, March 10, 2014 1:36:20 PM > Subject: Re: [Engine-devel] Supposed to add per CPU usage related infomation > into engine core and vdsm > > ----- Original Message ----- > > From: "Chuan Liao (Jason Liao, HPservers-Core-OE-PSC)" <[email protected]> > > To: "arch" <[email protected]>, "vdsm-devel" > > <[email protected]>, [email protected] > > Cc: "Gilad Chaplik" <[email protected]>, [email protected], > > [email protected] > > Sent: Monday, March 10, 2014 11:17:13 AM > > Subject: Supposed to add per CPU usage related infomation into engine core > > and vdsm > > > > Hi All, > > > > In order to support NUMA and guest NUMA feature in ovirt. > > We need per NUMA node CPU usage or per CPU usage related information on > > engine core. > > > > This information will be used for VM who have NUMA aware information and > > find > > the best Host to run it on with best performance. > > > > Approach 1: > > > > 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) > > > > 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, > > %idle) > > > > 3. Transport the usage data to engine core. > > > > 4. Engine core merge per NUMA node CPU usage. (%sys, %usr, %iowait, > > %idle) > > > > +1, since this data can be used for hardware other than NUMA
+1 , can be relevant to engine reports as well .... > > > Approach 2: > > > > 1. Sample data in vdsm for each CPU stats. (sys, usr, iowait, idle) > > > > 2. Calculate the each CPU usage information. (%sys, %usr, %iowait, > > %idle) > > > > 3. VDSM merge per NUMA node CPU usage. (%sys, %usr, %iowait, %idle) > > > > 4. Transport the usage data to engine core. > > > > Which one do you prefer, and why, or other solution. > > > > Best Regards, > > Jason Liao > > > > > _______________________________________________ > Engine-devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/engine-devel > _______________________________________________ Arch mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/arch
