From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: [PATCHv2 0/5] evtchn: Improve scalebility Date: Mon, 15 Jun 2015 16:48:14 +0100 Message-ID: <1434383299-21833-1-git-send-email-david.vrabel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z4XWH-00019E-Nh for xen-devel@lists.xenproject.org; Mon, 15 Jun 2015 16:45:57 +0000 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xenproject.org Cc: Keir Fraser , Tim Deegan , David Vrabel , Jan Beulich , Ian Campbell List-Id: xen-devel@lists.xenproject.org The per-domain event channel lock limits scalability when many VCPUs are trying to send interdomain events. A per-channel lock is introduced eliminating any lock contention when sending an event. See this graph for the performance improvements: http://xenbits.xen.org/people/dvrabel/evtchn-scalability.png A different test (using Linux's evtchn device which masks/unmasks event channels) showed the following lock profile improvements: Per-domain lock: (XEN) lock: 69267976(00000004:19830041), block: 27777407(00000002:3C7C5C96) Per-event channel lock (XEN) lock: 686530(00000000:076AF5F6), block: 1787(00000000:000B4D22) Locking removed from evtchn_unmask(): (XEN) lock: 10769(00000000:00512999), block: 99(00000000:00009491) v2: - Use unsigned int for d->valid_evtchns. - Compare channel pointers in double_evtchn_lock(). David