All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: netdev@vger.kernel.org
Cc: jasowang@redhat.com, mashirle@us.ibm.com
Subject: Re: [PULL net-next] vhost-net fixes for 3.1
Date: Tue, 19 Jul 2011 21:58:13 +0300	[thread overview]
Message-ID: <20110719185813.GA8632@redhat.com> (raw)
In-Reply-To: <20110719114741.GA5827@redhat.com>

On Tue, Jul 19, 2011 at 02:47:41PM +0300, Michael S. Tsirkin wrote:
> Here's Jason's fix for a theoretical event loss
> on migration (tweaked by me to update the test
> module as well), and a refcounting fix by me
> for a bug in the new zerocopy mode.
> 
> I thought hard about merging Jason's patches for 3.0
> as well, but in the end I think it's not worth
> the risk of breaking something at this stage.
> 
> Please pull for 3.1, thanks a lot!
> 
> The following changes since commit 81fc70d86527a1450560709500ca5f52e661da1f:
> 
>   net: can: remove custom hex_to_bin() (2011-07-18 11:31:43 -0700)
> 
> are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net-next
> 
> Jason Wang (2):
>       vhost: init used ring after backend was set
>       vhost: set log when updating used flags or avail event
> 
> Michael S. Tsirkin (1):
>       vhost: fix zcopy reference counting

I have snuck in another one:
	vhost: optimize interrupt enable/disable

please don't be alarmed :)

>  drivers/vhost/net.c   |    4 ++
>  drivers/vhost/test.c  |    5 +++
>  drivers/vhost/vhost.c |   87 ++++++++++++++++++++++++++++++------------------
>  drivers/vhost/vhost.h |    1 +
>  4 files changed, 64 insertions(+), 33 deletions(-)

  parent reply	other threads:[~2011-07-19 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 11:47 [PULL net-next] vhost-net fixes for 3.1 Michael S. Tsirkin
2011-07-19 17:15 ` David Miller
2011-07-19 18:58 ` Michael S. Tsirkin [this message]
2011-07-19 19:00   ` David Miller
2011-07-19 19:05     ` Michael S. Tsirkin

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=20110719185813.GA8632@redhat.com \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mashirle@us.ibm.com \
    --cc=netdev@vger.kernel.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 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.