Re: [Xen-devel] [PATCH 17/19] xen: credit2: the private scheduler lock can be an rwlock.

[George Dunlap <dunlapg@xxxxxxxxx>]

On Sat, Jun 18, 2016 at 12:13 AM, Dario Faggioli
<dario.faggioli@xxxxxxxxxx> wrote:
> In fact, the data it protects only change either at init-time,
> during cpupools manipulation, or when changing domains' weights.
> In all other cases (namely, load balancing, reading weights
> and status dumping), information is only read.
>
> Therefore, let the lock be an read/write one. This means there
> is no full serialization point for the whole scheduler and
> for all the pCPUs of the host any longer.
>
> This is particularly good for scalability (especially when doing
> load balancing).
>
> Also, update the high level description of the locking discipline,
> and take the chance for rewording it a little bit (as well as
> for adding a couple of locking related ASSERT()-s).
>
> Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx>

Looks good:

Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx>

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