<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Block on RESEARCHUT</title><link>https://researchut.com/tags/block/</link><description>Recent content in Block on RESEARCHUT</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>rrs@researchut.com (Ritesh Raj Sarraf)</managingEditor><webMaster>rrs@researchut.com (Ritesh Raj Sarraf)</webMaster><lastBuildDate>Fri, 26 Feb 2016 12:23:33 -0500</lastBuildDate><atom:link href="https://researchut.com/tags/block/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux IO + Memory + CPU Contention</title><link>https://researchut.com/blog/linux-large-io-bug/</link><pubDate>Fri, 26 Feb 2016 12:23:33 -0500</pubDate><author>rrs@researchut.com (Ritesh Raj Sarraf)</author><guid>https://researchut.com/blog/linux-large-io-bug/</guid><description>&lt;p>I very recently met someone, and we had a good productive discussion on the
features and (long standing) bugs of the Linux kernel. No doubt, Linux is the
most featureful kernel in the market. Is also a lot appealing given its
breadth of platform support.&lt;/p>
&lt;p>Of that discussion we had, it led about Linux&amp;rsquo;s behavior in tighter stressed
scenarios where there is a lot of contention among the core subsystems. From
the conversation, I got the feedback that perhaps the
&lt;a href="https://bugzilla.kernel.org/show_bug.cgi?id=12309">issue&lt;/a> is no more valid.
My conclusion was I must have missed out on the fix because I haven&amp;rsquo;t really
spent any Engineering Lab time in recent past.&lt;/p>
&lt;p>But a picture says a thousand words. And no, the issue is NOT fixed. And it is
still simple to reproduce the bug. And it is just that we have faster
advancements in underlying hardware, that we may eventually find it much
harder to reproduce these bugs.&lt;/p>
&lt;p>&lt;img src="https://researchut.com/images/IMG_20160226_223108.jpg" alt="">&lt;/p>
&lt;p>The kernel spitting the screen is Linux 4.4 Stock Debian.&lt;/p></description></item></channel></rss>