From: Zachary Amsden <zach@vmware.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, chrisw@sous-sol.org,
jeremy@xensource.com, rusty@rustcorp.com.au
Subject: Re: + paravirt-vmi-timer-patches.patch added to -mm tree
Date: Sat, 06 Jan 2007 12:51:57 -0800 [thread overview]
Message-ID: <45A00BED.6030802@vmware.com> (raw)
In-Reply-To: <1168116057.26086.227.camel@imap.mvista.com>
Daniel Walker wrote:
> On Sat, 2007-01-06 at 12:37 -0800, Zachary Amsden wrote:
>
>
>>> There is already a dynamic tick (NO_HZ) system in the -mm tree .. Given
>>> that this implementation seems unnecessary. Why do you need another
>>> different system to do this?
>>>
>>>
>> We don't. This was written before the dynamic tick code, and now they
>> need to be merged. Until then, they can safely coexist.
>>
>
> So really this can't go upstream till that merge happens. What's
> preventing you from just directly using NO_HZ without changes?
>
For one thing, the fact that it doesn't account for stolen time. But
mostly because going through the regular PIT / APIC timer paths has a
lot of overhead. So we need a separate timer device, and weaving this
in with the local APIC timer dependency for SMP on i386 requires changes
on top of NO_HZ.
Zach
prev parent reply other threads:[~2007-01-06 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 22:27 + paravirt-vmi-timer-patches.patch added to -mm tree akpm
2007-01-06 16:54 ` Daniel Walker
2007-01-06 20:52 ` Zachary Amsden
2007-01-06 18:06 ` Daniel Walker
2007-01-06 20:37 ` Zachary Amsden
2007-01-06 20:40 ` Daniel Walker
2007-01-06 20:51 ` Zachary Amsden [this message]
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=45A00BED.6030802@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=dwalker@mvista.com \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.