Editing I/O priorities
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 13: | Line 13: | ||
The higher the value you use, the more I/O time your container will receive. | The higher the value you use, the more I/O time your container will receive. | ||
| − | The mapping from priority to time is the following: if <tt>0</tt> prio corresponds to time slice <tt>t</tt>, | + | The mapping from priority to time is the following: if <tt>0</tt> prio corresponds to time slice <tt>t</tt>, than <tt>8</tt> prio corresponds to time slice <tt>2 * t</tt>. Default time slice value is <tt>HZ/2</tt>. The main criteria for fairness at the moment is that if you set I/O prio of CT 1 to <tt>p1</tt> and I/O prio of CT 2 to <tt>p2</tt>, and <tt>p1 > p2</tt> then CT 1 should do more I/O than CT 2. In simple form the priorities are relative with the higher priority getting more I/O time. |
== See also == | == See also == | ||
