[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] evtchn: eliminate 64k ports limitation

To: Jan Beulich <JBeulich@xxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Wed, 2 Apr 2014 10:36:41 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, David Vrabel <david.vrabel@xxxxxxxxxx>
Delivery-date: Wed, 02 Apr 2014 09:36:59 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 02/04/14 09:03, Jan Beulich wrote:
> The introduction of FIFO event channels claimed to support over 100k
> ports, but failed to widen a number of 16-bit variables/operations.

Reviewed-by: David Vrabel <david.vrabel@xxxxxxxxxx>

Thanks.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH] evtchn: eliminate 64k ports limitation
  - From: Jan Beulich

Prev by Date: Re: [Xen-devel] [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
Next by Date: Re: [Xen-devel] [PATCH v4 4/7] xen, common: add the XEN_DOMCTL_memory_mapping hypercall
Previous by thread: [Xen-devel] [PATCH] evtchn: eliminate 64k ports limitation
Next by thread: Re: [Xen-devel] [PATCH] evtchn: eliminate 64k ports limitation
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.