[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140329144607.GA20316@amt.cnet>
Date: Sat, 29 Mar 2014 11:46:07 -0300
From: Marcelo Tosatti <mtosatti@...hat.com>
To: Zhanghailiang <zhang.zhanghailiang@...wei.com>
Cc: "johnstul@...ibm.com" <johnstul@...ibm.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Zhouxiangjiu <zhouxiangjiu@...wei.com>,
zhang yanying <zhuangyanying@...wei.com>
Subject: Re: VDSO pvclock may increase host cpu consumption, is this a
problem?
On Sat, Mar 29, 2014 at 08:47:27AM +0000, Zhanghailiang wrote:
> Hi,
> I found when Guest is idle, VDSO pvclock may increase host consumption.
> We can calcutate as follow, Correct me if I am wrong.
> (Host)250 * update_pvclock_gtod = 1500 * gettimeofday(Guest)
> In Host, VDSO pvclock introduce a notifier chain, pvclock_gtod_chain in timekeeping.c. It consume nearly 900 cycles per call. So in consideration of 250 Hz, it may consume 225,000 cycles per second, even no VM is created.
> In Guest, gettimeofday consumes 220 cycles per call with VDSO pvclock. If the no-kvmclock-vsyscall is configured, gettimeofday consumes 370 cycles per call. The feature decrease 150 cycles consumption per call.
> When call gettimeofday 1500 times,it decrease 225,000 cycles,equal to the host consumption.
> Both Host and Guest is linux-3.13.6.
> So, whether the host cpu consumption is a problem?
Hi,
How many percents out of the total CPU cycles are 225,000 cycles, for your
CPU ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists