 Home |
Products |
Support |
Community |
News |
xen-users
Re: [Xen-users] heavy write crashing, was: process limit
| To: | Tim Freeman <tfreeman@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-users] heavy write crashing, was: process limit |
| From: | Anand <xen.mails@xxxxxxxxx> |
| Date: | Sat, 14 Jan 2006 03:12:45 +0530 |
| Cc: | xen-users@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Fri, 13 Jan 2006 21:49:44 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=FJHpoZgW2USb+b2xb9kbcz4JVStn/D0fKvBTHTtK41IT964vbavJxG6kXfIbkGxkXZzEypZHjxDdT0Anpm6aSKkz6Vcej/08l5a/JdNnxuNFN4dRNgtHzoWnQ9YKxAl8+PtLJNS5AxppUeKcoSxUvnWOWw8ZHMZTnm8OLH3lB5c= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20060113153438.6aa996c6.tfreeman@xxxxxxxxxxx> |
| List-help: | <mailto:xen-users-request@lists.xensource.com?subject=help> |
| List-id: | Xen user discussion <xen-users.lists.xensource.com> |
| List-post: | <mailto:xen-users@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe> |
| References: | <20060111204116.2fa270a9.tfreeman@xxxxxxxxxxx> <acb757c00601131331y7bf4a055s5813a2cc8a3b234@xxxxxxxxxxxxxx> <20060113153438.6aa996c6.tfreeman@xxxxxxxxxxx> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
On 1/14/06, Tim Freeman <tfreeman@xxxxxxxxxxx> wrote:Yes, the disk I/O scheduling entry on the Xen roadmap is very interesting to us! I read that as well. This is something which is really required since any IO intensive process can create havoc for the entire host and other domU's. I noticed during the domU bootup, the bootup messages contains info about IO schedulers however they don't seem to be working as of now. You can pass elevator=io_scheduler_name to the kernel to change the io scheduler (i posted this information in another message to the list). My guess is they should be using the linux IO scheduler code directly since its something which is already available. On top some more features could be added which can help restrict IO on some domains. -- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-users] heavy write crashing, was: process limit, Tim Freeman |
|---|---|
| Next by Date: | Re: [Xen-users] heavy write crashing, was: process limit, Tim Freeman |
| Previous by Thread: | Re: [Xen-users] heavy write crashing, was: process limit, Tim Freeman |
| Next by Thread: | Re: [Xen-users] heavy write crashing, was: process limit, Tim Freeman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
