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] more linux balloon driver questions

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] more linux balloon driver questions
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 26 Aug 2010 15:47:19 -0700 (PDT)
Cc: jeremy@xxxxxxxx, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Thu, 26 Aug 2010 15:50:22 -0700
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
Linux balloon driver experts --

I see that balloon work-to-do is put on the default
keventd work queue, which also means that it is
queued on each cpu.  Is there a good reason for this
as opposed to putting it on a separate work queue
and on a single cpu (i.e. create_singlethread_workqueue)?

Thanks,
Dan

P.S. I think I solved my other problem... I had
added work to the keventd work queue which
under some circumstances was blocking.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] more linux balloon driver questions, Dan Magenheimer <=