24.12.2012 Views

Chapter 4 - DSpace at Waseda University

Chapter 4 - DSpace at Waseda University

Chapter 4 - DSpace at Waseda University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

71<br />

<strong>Chapter</strong> 5<br />

Figure 5.11 is the d<strong>at</strong>a showing the part where HRTimer l<strong>at</strong>ency occurred. According to the<br />

result of AL, events such as net_socket_sending, net_dev_xmit, and mm_page_alloc have the<br />

occurred a lot. These events were oper<strong>at</strong>ed before the HRTimer event (HRTIMER_SOFTIRQ)<br />

was processed and according to the analysis of the kernel source, these events have higher<br />

priority than softriq of HRTimer.<br />

Figure 5.12 shows the result analyzed based on event logs is Figure 5.11. Figure 5.12 shows<br />

how HRTimer analyzes its l<strong>at</strong>ency. In the process of executing, between each softirq handler<br />

execution, HRTimer softirq (HRTIMER_SOFTIRQ) is executed. We can find th<strong>at</strong><br />

run_hrtimer_softirq() occurred after net_dev_xmit (NET_TX_SOFTIRQ) and mm_page_alloc<br />

(BLOCK_SOFTIRQ) th<strong>at</strong> is higher priority than HRTimer softirq.<br />

Figure 5.12: One of the reasons of HRTimer l<strong>at</strong>ency<br />

Therefore, Figure 5.13 shows process of interrupt in timeline. When softriq with high<br />

priority is in progress, softriq with low priority cannot be executed. After the high priority<br />

softriq is finished, the low priority (HRTimer softriq) is executed.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!