virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, mst@redhat.com,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [V5 PATCH] virtio-net: send gratuitous packets when needed
Date: Wed, 28 Mar 2012 10:35:53 +0800	[thread overview]
Message-ID: <4F727909.5050609@redhat.com> (raw)
In-Reply-To: <20120327.223112.2032989102915830685.davem@davemloft.net>

On 03/28/2012 10:31 AM, David Miller wrote:
> From: Jason Wang<jasowang@redhat.com>
> Date: Fri, 16 Mar 2012 17:01:01 +0800
>
>> >  As hypervior does not have the knowledge of guest network configuration, it's
>> >  better to ask guest to send gratuitous packets when needed.
>> >  
>> >  Guest tests VIRTIO_NET_S_ANNOUNCE bit during config change interrupt and when it
>> >  is set, a workqueue is scheduled to send gratuitous packet through
>> >  NETDEV_NOTIFY_PEERS. This feature is negotiated through bit
>> >  VIRTIO_NET_F_GUEST_ANNOUNCE.
>> >  
>> >  Changes from v4:
>> >  - typos
>> >  - handle workqueue unconditionally
>> >  - move VIRTIO_NET_S_ANNOUNCE to bit 8 to separate rw bits from ro bits
>> >  
>> >  Changes from v3:
>> >  - cancel the workqueue during freeze
>> >  
>> >  Changes from v2:
>> >  - fix the race between unregister_dev() and workqueue
>> >  
>> >  Signed-off-by: Jason Wang<jasowang@redhat.com>
> What's happening with this patch?
Hi David:

I'm working on a new version of this patch as there's some changes in 
virtio-spec, I would post it soon.

Thanks

      reply	other threads:[~2012-03-28  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  9:01 [V5 PATCH] virtio-net: send gratuitous packets when needed Jason Wang
2012-03-28  2:31 ` David Miller
2012-03-28  2:35   ` Jason Wang [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=4F727909.5050609@redhat.com \
    --to=jasowang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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).