From: Eric Blake <eblake@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Amos Kong <akong@redhat.com>,
qemu-devel@nongnu.org, stefanha@redhat.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/2] net: introduce MAC_TABLE_CHANGED event
Date: Thu, 16 May 2013 08:58:38 -0600 [thread overview]
Message-ID: <5194F41E.3020501@redhat.com> (raw)
In-Reply-To: <20130516121745.GE31841@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
On 05/16/2013 06:17 AM, Michael S. Tsirkin wrote:
> On Thu, May 16, 2013 at 07:07:24PM +0800, Amos Kong wrote:
>> Introduce this new QMP event to notify management after guest changes
>> mac-table configuration.
>>
>
> This makes it easy for guest to flood management with
> spurious events.
> How about we set a flag after this, and avoid sending any more
> events until management queries the filter status?
>
Or use rate-limiting, similar to what we have done for other
guest-triggered events (such as BALLOON_CHANGE), where management can
then tweak the maximum frequency at which it is willing to receive events.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-05-16 14:58 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 11:07 [Qemu-devel] [PATCH v2 0/2] mac programming over macvtap Amos Kong
2013-05-16 11:07 ` [Qemu-devel] [PATCH v2 1/2] net: introduce MAC_TABLE_CHANGED event Amos Kong
2013-05-16 12:12 ` Michael S. Tsirkin
2013-05-16 12:17 ` Michael S. Tsirkin
2013-05-16 12:24 ` Luiz Capitulino
2013-05-16 12:45 ` Michael S. Tsirkin
2013-05-16 12:52 ` Luiz Capitulino
2013-05-16 14:58 ` Eric Blake [this message]
2013-05-16 15:03 ` Michael S. Tsirkin
2013-05-16 15:06 ` Michael S. Tsirkin
2013-05-16 15:12 ` Eric Blake
2013-05-16 15:17 ` Michael S. Tsirkin
2013-05-16 15:24 ` Eric Blake
2013-05-23 15:54 ` Luiz Capitulino
2013-05-23 17:18 ` Michael S. Tsirkin
2013-05-23 17:26 ` Luiz Capitulino
2013-05-24 12:10 ` Michael S. Tsirkin
2013-05-24 12:51 ` Luiz Capitulino
2013-05-27 9:34 ` Amos Kong
2013-05-27 13:10 ` Luiz Capitulino
2013-05-27 13:24 ` Luiz Capitulino
2013-05-27 22:43 ` Amos Kong
2013-05-28 12:25 ` Luiz Capitulino
2013-05-30 13:50 ` Amos Kong
2013-05-30 13:57 ` Michael S. Tsirkin
2013-05-30 13:54 ` Michael S. Tsirkin
2013-05-31 0:35 ` Amos Kong
2013-05-31 3:02 ` Amos Kong
2013-06-04 6:43 ` Amos Kong
2013-06-04 7:42 ` Amos Kong
2013-06-04 11:11 ` Michael S. Tsirkin
2013-05-21 5:04 ` Amos Kong
2013-05-21 8:51 ` Michael S. Tsirkin
2013-05-23 6:08 ` Amos Kong
2013-05-16 14:56 ` Eric Blake
2013-05-16 15:01 ` Michael S. Tsirkin
2013-05-16 11:07 ` [Qemu-devel] [PATCH v2 2/2] net: introduce command to query mac-table information Amos Kong
2013-05-16 12:19 ` Michael S. Tsirkin
2013-05-21 3:31 ` Amos Kong
2013-05-16 15:38 ` Eric Blake
2013-05-23 4:03 ` Amos Kong
2013-05-17 7:39 ` Stefan Hajnoczi
2013-05-21 4:46 ` Amos Kong
2013-05-21 7:38 ` Stefan Hajnoczi
2013-05-29 5:31 ` Jason Wang
2013-06-05 7:18 ` Amos Kong
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=5194F41E.3020501@redhat.com \
--to=eblake@redhat.com \
--cc=akong@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).