WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon

To: Jared Rhine <jared@xxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Mon, 24 Jan 2005 13:11:12 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Jan 2005 18:44:31 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <871xcag1f4.wl@xxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: IBM
References: <1106322956.17263.26.camel@localhost> <eacc82a4050121083937725a83@xxxxxxxxxxxxxx> <Pine.LNX.4.58.0501211016500.4841@xxxxxxxxxx> <1106337581.18070.13.camel@localhost> <Pine.LNX.4.58.0501211343530.5215@xxxxxxxxxx> <1106342088.18665.1.camel@localhost> <Pine.LNX.4.58.0501211353100.5215@xxxxxxxxxx> <1106343476.7691.91.camel@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0501240829570.12186@xxxxxxxxxxxxxxxxxx> <1106584520.18665.10.camel@localhost> <1106585752.17408.16.camel@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0501240957520.12186@xxxxxxxxxxxxxxxxxx> <871xcag1f4.wl@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On Mon, 2005-01-24 at 11:52, Jared Rhine wrote:
>   Ronald> The issue is that, in any large scale cluster, if you have
>   Ronald> enough processes running besides your application on the
>   Ronald> nodes, then the act of scheduling those processes -- even
>   Ronald> for select calls that return instantly
>   Ronald> -- can derange the application performance.

This is why schedulers have priority.  Just bump up the priority of your
desired app.  Also, with the Linux O(1) scheduler, a process blocked on
I/O (at least, by my understanding) should have no impact on other
processes scheduling.

-- 
Anthony Liguori
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@xxxxxxxxxx
Phone: (512) 838-1208




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>