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

Re: [Xen-devel] [PATCH 2 of 4 RFC] blktap3/sring: extract requests from the ring, grouping of VBDs


  • To: Thanos Makatos <thanos.makatos@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxxx>
  • Date: Thu, 14 Mar 2013 17:24:47 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Thu, 14 Mar 2013 17:25:10 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac4fISFZWKFkzaVPQd+MVve6yUjL4gBt0crA
  • Thread-topic: [PATCH 2 of 4 RFC] blktap3/sring: extract requests from the ring, grouping of VBDs

> Also, there is another piece of functionality introduced for which I
> have some
> questions: two or more VBDs served by the same tapdisk process can be
> grouped into a "context". This context carries the handle to the event
> channel driver used to bind to the guest domain's port in order to
> receive/send notifications for the shared ring. I don't see any merit
> by this grouping and I think it should be removed, is there something I
> am overseeing?

Actually, I think I just realized what's the purpose of this grouping: reduce 
the number of event channels used for sring notifications, right? Correct me if 
I'm wrong but is there some ongoing work on increasing the number of event 
channels, rendering this optimisation useless?

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


 


Rackspace

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