From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: kvm@vger.kernel.org, virtualization@lists.osdl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
eric.dumazet@gmail.com, jasowang@redhat.com, krkumar2@in.ibm.com,
mst@redhat.com
Subject: [PULL net-2.6] vhost: cleanups and fixes
Date: Thu, 17 Mar 2011 16:04:04 +0200 [thread overview]
Message-ID: <20110317140403.GA16390@redhat.com> (raw)
The following tree has fixes for vhost-net for 2.6.39.
These are easier to apply on top of Jason's and Krishna's
cleanups, and they got tested this way, so I thought it's
better for everyone to include that, and the trivial
copy_from_user optimization.
But if you think it's too late for that, pls let me know
and I'll try to untangle that dependency.
Thanks!
The following changes since commit 1fc050a13473348f5c439de2bb41c8e92dba5588:
ipv4: Cache source address in nexthop entries. (2011-03-07 20:54:48 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net-next
Jason Wang (3):
vhost-net: check the support of mergeable buffer outside the receive loop
vhost-net: Unify the code of mergeable and big buffer handling
vhost: lock receive queue, not the socket
Krishna Kumar (1):
vhost: Cleanup vhost.c and net.c
Michael S. Tsirkin (2):
vhost: copy_from_user -> __copy_from_user
vhost-net: remove unlocked use of receive_queue
drivers/vhost/net.c | 159 ++++++++-----------------------------------------
drivers/vhost/vhost.c | 55 ++++++++++++-----
2 files changed, 64 insertions(+), 150 deletions(-)
next reply other threads:[~2011-03-17 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:04 Michael S. Tsirkin [this message]
2011-03-21 2:08 ` [PULL net-2.6] vhost: cleanups and fixes David Miller
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=20110317140403.GA16390@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jasowang@redhat.com \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.osdl.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.