<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://kerneltrap.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>KernelTrap - dyntick</title>
 <link>http://kerneltrap.org/taxonomy/term/387/0</link>
 <description></description>
 <language>en-local</language>
<item>
 <title>Linux:  2.6.21 Kernel Released</title>
 <link>http://kerneltrap.org/node/8103</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Linux creator Linus Torvalds announced the release of the 2.6.21 kernel, &quot;&lt;i&gt;if the goal for 2.6.20 was to be a stable release (and it was), the goal for 2.6.21 is to have just survived the big timer-related changes and some of the other surprises (just as an example: we were apparently unlucky enough to hit what looks like a previously unknown hardware errata in one of the ethernet drivers that got updated etc).&lt;/i&gt;&quot;  Regarding the the dynticks code which was merged in -rc1 [&lt;a href=&quot;http://kerneltrap.org/node/7749&quot;&gt;story&lt;/a&gt;] he said, &quot;&lt;i&gt;the big change during 2.6.21 is all the timer changes to support a tickless system (and even with ticks, more varied time sources). Thanks (when it no longer broke for lots of people ;) go to Thomas Gleixner and Ingo Molnar and a cadre of testers and coders.&lt;/i&gt;&quot;  He went on to note, &quot;&lt;i&gt;of course, the timer stuff was just the most painful and core part (and thus the one that I remember most): there&#039;s a lot of changes all over. The appended changelog is just for the fixes since -rc7, so that doesn&#039;t look very impressive, the full changes since 2.6.20 are obviously a *lot* bigger (and you&#039;re better off reading the individual -rc changelogs).&lt;/i&gt;&quot;  Linus finished with a running joke about the many debates centered around current CPU scheduler efforts [&lt;a href=&quot;http://kerneltrap.org/node/8082&quot;&gt;story&lt;/a&gt;], quipping, &quot;&lt;i&gt;we now return you to your regular scheduler discussions&lt;/i&gt;&quot;.&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://kerneltrap.org/node/8103&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://kerneltrap.org/node/8103#comments</comments>
 <category domain="http://kerneltrap.org/2.6.20">2.6.20</category>
 <category domain="http://kerneltrap.org/2.6.21">2.6.21</category>
 <category domain="http://kerneltrap.org/taxonomy/term/387">dyntick</category>
 <category domain="http://kerneltrap.org/Ingo_Molnar">Ingo Molnar</category>
 <category domain="http://kerneltrap.org/Linus_Torvalds">Linus Torvalds</category>
 <category domain="http://kerneltrap.org/Linux">Linux</category>
 <category domain="http://kerneltrap.org/release">release</category>
 <category domain="http://kerneltrap.org/scheduler">scheduler</category>
 <category domain="http://kerneltrap.org/Thomas_Gleixner">Thomas Gleixner</category>
 <category domain="http://kerneltrap.org/tickless">tickless</category>
 <category domain="http://kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Thu, 26 Apr 2007 09:58:27 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">8103 at http://kerneltrap.org</guid>
</item>
<item>
 <title>Linux:  Improving KVM Performance With A Tickless Kernel</title>
 <link>http://kerneltrap.org/node/7568</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Avi Kivity suggested that combining KVM, the Kernel-based Virtual Machine [&lt;a href=&quot;&quot;&gt;story&lt;/a&gt;], with the dyntick patch [&lt;a href=&quot;http://kerneltrap.org/node/6750&quot;&gt;story&lt;/a&gt;] could improve overall KVM performance.  He noted that it would likely improve performance of both the host by &quot;&lt;i&gt;avoiding expensive vmexits due to useless timer interrupts,&lt;/i&gt;&quot; as well as on the guest by &quot;&lt;i&gt;reducing the load on the host when the guest is idling (currently an idle guest consumes a few percent cpu)&lt;/i&gt;&quot;.  Ingo Molnar [&lt;a href=&quot;http://kerneltrap.org/node/view/517&quot;&gt;interview&lt;/a&gt;] pointed out that KVM with his -rt kernel already works with dynticks enabled on both the host and the guest, &quot;&lt;i&gt;using the dynticks code from the -rt kernel makes the overhead of an  idle guest go down by a factor of 10-15&lt;/i&gt;&quot;.  Ingo added that he hopes the dyntick patch will be ready to be merged into the upcoming mainline 2.6.21 kernel.&lt;/p&gt;
&lt;p&gt;Rik van Riel [&lt;a href=&quot;http://kerneltrap.org/node/view/46&quot;&gt;interview&lt;/a&gt;] noted that there were other ways to reduce the load of the guest when it&#039;s idling, &quot;&lt;i&gt;you do not need dynticks for this actually.  Simple no-tick-on-idle like Xen has works well enough.&lt;/i&gt;&quot;  Ingo explained, &quot;&lt;i&gt;s390 (and more recently Xen too) uses a next_timer_interrupt() based method to stop the guest tick - which works in terms of reducing guest load, but it doesnt stop the host-side interrupt. The highest quality approach is to have dynticks on both the host and the guest, and this also gives high-resolution timers and a modernized time/timer-events subsystem for both the host and the guest.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://kerneltrap.org/node/7568&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://kerneltrap.org/node/7568#comments</comments>
 <category domain="http://kerneltrap.org/taxonomy/term/352">Avi Kivity</category>
 <category domain="http://kerneltrap.org/taxonomy/term/387">dyntick</category>
 <category domain="http://kerneltrap.org/kvm">kvm</category>
 <category domain="http://kerneltrap.org/Linux">Linux</category>
 <category domain="http://kerneltrap.org/Rik_van_Riel">Rik van Riel</category>
 <category domain="http://kerneltrap.org/tickless">tickless</category>
 <category domain="http://kerneltrap.org/virtual_machine">virtual machine</category>
 <category domain="http://kerneltrap.org/Xen">Xen</category>
 <category domain="http://kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Sat, 13 Jan 2007 09:56:59 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">7568 at http://kerneltrap.org</guid>
</item>
<item>
 <title>Linux:  High-Res Timers and Tickless Kernel</title>
 <link>http://kerneltrap.org/node/6750</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Thomas Gleixner and Ingo Molnar [&lt;a href=&quot;http://kerneltrap.org/node/view/517&quot;&gt;interview&lt;/a&gt;] posted an update of their high-res timers &lt;a href=&quot;http://www.tglx.de/projects/hrtimers/2.6.17/&quot; target=&quot;new&quot;&gt;kernel patches&lt;/a&gt; for the 2.6.17 kernel, &quot;&lt;i&gt;upon which we based a tickless kernel (dyntick) implementation and a &#039;dynamic HZ&#039; feature as well&lt;/i&gt;&quot;.  The patch currently works for x86, with ports to x86_64, PPC and ARM in the works.  Thomas explains, &quot;&lt;i&gt;the high-res timers feature (CONFIG_HIGH_RES_TIMERS) enables POSIX timers and nanosleep() to be as accurate as the hardware allows (around 