Re: [Xen-devel] [PATCHv1 net] xen-netback: notify immediately after pushing Tx response.

2015-03-11 Thread Zoltan Kiss
On 11/03/15 15:27, David Vrabel wrote: This fixes a performance regression introduced by 7fbb9d8415d4a51cf542e87cf3a717a9f7e6aedc (xen-netback: release pending index before pushing Tx responses) Moving the notify outside of the spin locks means it can be delayed a long time (if the dealloc

[Xen-devel] [PATCHv1 net] xen-netback: notify immediately after pushing Tx response.

2015-03-11 Thread David Vrabel
This fixes a performance regression introduced by 7fbb9d8415d4a51cf542e87cf3a717a9f7e6aedc (xen-netback: release pending index before pushing Tx responses) Moving the notify outside of the spin locks means it can be delayed a long time (if the dealloc thread is descheduled or there is an

Re: [Xen-devel] [PATCHv1 net] xen-netback: notify immediately after pushing Tx response.

2015-03-11 Thread Wei Liu
On Wed, Mar 11, 2015 at 03:27:59PM +, David Vrabel wrote: This fixes a performance regression introduced by 7fbb9d8415d4a51cf542e87cf3a717a9f7e6aedc (xen-netback: release pending index before pushing Tx responses) Moving the notify outside of the spin locks means it can be delayed a

Re: [Xen-devel] [PATCHv1 net] xen-netback: notify immediately after pushing Tx response.

2015-03-11 Thread David Miller
From: David Vrabel david.vra...@citrix.com Date: Wed, 11 Mar 2015 15:27:59 + This fixes a performance regression introduced by 7fbb9d8415d4a51cf542e87cf3a717a9f7e6aedc (xen-netback: release pending index before pushing Tx responses) Moving the notify outside of the spin locks means it