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 1: | Line 1: | ||
| − | The I/O priorities feature is implemented in OpenVZ since kernel <tt>2.6.18- | + | The I/O priorities feature is implemented in OpenVZ since kernel <tt>2.6.18-028stable021</tt>, <tt>vzctl 3.0.16</tt>. This feature allows to assign I/O priority to any [[container]]. Priority range is <tt>0-7</tt>. The more priority a container has, the more time for using block devices this container will obtain. This feature is based on CFQ I/O scheduler, so this scheduler should be used for block device in question. Default I/O priority is <tt>4</tt>. Examples of using: |
| − | |||
| − | |||
| − | |||
vzctl set 101 --ioprio 0 --save | vzctl set 101 --ioprio 0 --save | ||
| − | |||
vzctl set 101 --ioprio 7 --save | vzctl set 101 --ioprio 7 --save | ||
| − | + | 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. | |
| − | + | == See also == | |
| − | |||
| − | |||
| − | |||
| − | |||
* [[IO accounting]] | * [[IO accounting]] | ||
[[Category: Resource management]] | [[Category: Resource management]] | ||
| − | |||
