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

[Xen-devel] [PATCH 0 of 2] credit2: Reduce excessive cpu migration

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 0 of 2] credit2: Reduce excessive cpu migration
From: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Date: Thu, 9 Dec 2010 17:55:15 +0000
Cc: george.dunlap@xxxxxxxxxxxxx
Delivery-date: Thu, 09 Dec 2010 10:07:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mercurial-patchbomb/1.4.3
More recent processors have one L2 per core.  My plan for the credit2
scheduler invovled having several cores sharing the same runqueue.

I've measured the cost of excessive cross-L2 intra-L3 migrations, and while
they're not excessive, they are measurable.  This patch series introduces
some simple heuristics to reduce unnecessary migration.

As in all the Credit2 work, this is a first cut, and I'm sure there are
further improvments.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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