From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Campbell <Ian.Campbell@eu.citrix.com>Ian,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Register watches for frontend features.
Date: Sat, 10 Jul 2010 10:30:47 -0700 [thread overview]
Message-ID: <4C38AE47.9020009@goop.org> (raw)
In-Reply-To: <291EDFCB1E9E224A99088639C47620227A476E6810@LONPMAILBOX01.citrite.net>
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
prev parent reply other threads:[~2010-07-10 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 11:39 [PATCH] Register watches for frontend features Paul Durrant
2010-07-07 18:10 ` Jeremy Fitzhardinge
2010-07-09 12:53 ` Paul Durrant
2010-07-10 17:30 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C38AE47.9020009@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.