From: Amos Kong <akong@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: mst@redhat.com, stefanha@redhat.com, qemu-devel@nongnu.org,
laine@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6] net: add support of mac-programming over macvtap in QEMU side
Date: Tue, 18 Jun 2013 11:00:18 +0800 [thread overview]
Message-ID: <20130618030018.GA6038@amosk.info> (raw)
In-Reply-To: <51BFBEEE.8060803@linux.vnet.ibm.com>
On Tue, Jun 18, 2013 at 09:59:10AM +0800, Wenchao Xia wrote:
> 于 2013-6-14 15:45, Amos Kong 写道:
> > Currently macvtap based macvlan device is working in promiscuous
> > mode, we want to implement mac-programming over macvtap through
> > Libvirt for better performance.
> >
> > Design:
> > QEMU notifies Libvirt when rx-filter config is changed in guest,
> > then Libvirt query the rx-filter information by a monitor command,
> > and sync the change to macvtap device. Related rx-filter config
> > of the nic contains main mac, rx-mode items and vlan table.
> >
> > This patch adds a QMP event to notify management of rx-filter change,
> > and adds a monitor command for management to query rx-filter
> > information.
> >
> > Test:
> > If we repeatedly add/remove vlan, and change macaddr of vlan
> > interfaces in guest by a loop script.
> >
> > Result:
> > The events will flood the QMP client(management), management takes
> > too much resource to process the events.
> >
> > Event_throttle API (set rate to 1 ms) can avoid the events to flood
> > QMP client, but it could cause an unexpected delay (~1ms), guests
> > guests normally expect rx-filter updates immediately.
> >
> > So we use a flag for each nic to avoid events flooding, the event
> > is emitted once until the query command is executed. The flag
> > implementation could not introduce unexpected delay.
> >
> > There maybe exist an uncontrollable delay if we let Libvirt do the
> > real change, guests normally expect rx-filter updates immediately.
> > But it's another separate issue, we can investigate it when the
> > work in Libvirt side is done.
> >
> Hi, Amos
> This patch is for the user case that guest use a macvtap device right?
> could u add some document in commit message, so reader can understand
> what it trying to do?
I will add a single document later for it.
docs/macprogramming-over-macvtap.txt
Thanks.
> Wenchao Xia
--
Amos.
prev parent reply other threads:[~2013-06-18 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 7:45 [Qemu-devel] [PATCH v6] net: add support of mac-programming over macvtap in QEMU side Amos Kong
2013-06-17 13:11 ` Luiz Capitulino
2013-06-17 13:21 ` Michael S. Tsirkin
2013-06-17 13:30 ` Luiz Capitulino
2013-06-17 14:20 ` Michael S. Tsirkin
2013-06-17 14:34 ` Luiz Capitulino
2013-06-17 14:42 ` Michael S. Tsirkin
2013-06-17 14:54 ` Luiz Capitulino
2013-06-17 15:03 ` Amos Kong
2013-06-17 15:10 ` Michael S. Tsirkin
2013-06-17 15:15 ` Luiz Capitulino
2013-06-17 14:50 ` Amos Kong
2013-06-17 13:52 ` Michael S. Tsirkin
2013-06-18 1:59 ` Wenchao Xia
2013-06-18 3:00 ` Amos Kong [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=20130618030018.GA6038@amosk.info \
--to=akong@redhat.com \
--cc=laine@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiawenc@linux.vnet.ibm.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).