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

Re: [Xen-devel] [PATCH RFC] xen/evtchn: Implement EVTCHNOP_send_imm as a companian to EVTCHNOP_send



> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of Jan
> Beulich
> Sent: 13 July 2017 21:36
> To: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>
> Cc: Juergen Gross <jgross@xxxxxxxx>; sstabellini@xxxxxxxxxx; Wei Liu
> <wei.liu2@xxxxxxxxxx>; xen-devel@xxxxxxxxxxxxx; julien.grall@xxxxxxx;
> Roger Pau Monne <roger.pau@xxxxxxxxxx>
> Subject: Re: [Xen-devel] [PATCH RFC] xen/evtchn: Implement
> EVTCHNOP_send_imm as a companian to EVTCHNOP_send
> 
> >>> Andrew Cooper <andrew.cooper3@xxxxxxxxxx> 07/13/17 9:50 AM >>>
> >RFC: is it worth converting the close, unmask, reset (and possibly
> >expand_array) as well?
> 
> I can't see close and even more so reset to be performance critical.
> Unmask otoh may be (depending on use); no sure about expand_array.
>

IIRC the unmask hypercall only needs to be made in certain circumstances when 
direct unmasking of the fifo structure might race (can't remember the detail 
offhand), but it still seems like a reasonable target for an immediate argument.

  Paul
 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

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