From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] Register watches for frontend features. Date: Sat, 10 Jul 2010 10:30:47 -0700 Message-ID: <4C38AE47.9020009@goop.org> References: <1278329973-12414-1-git-send-email-paul.durrant@citrix.com> <4C34C320.2010102@goop.org> <291EDFCB1E9E224A99088639C47620227A476E6810@LONPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <291EDFCB1E9E224A99088639C47620227A476E6810@LONPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Paul Durrant Cc: Campbell Ian, "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 07/09/2010 05:53 AM, Paul Durrant wrote: > Realistically, with a Windows frontend, the only ones that are going to change dynamically are gso_prefix and csum. I can 'de-watch' the others, if you'd prefer. > As for locking, it's not clear to me how fatal getting netbk_max_required_rx_slots wrong is. However, losing or gaining gso/gso_prefix part way through a receive is not going to be good so I thing some double buffering is probably called for. I'll re-work the patch accordingly. > Yes. Given that those are guest-controlled, dom0 needs to be very careful in how it handles them. J