From: "Michael S. Tsirkin" <mst@redhat.com>
To: Krishna Kumar2 <krkumar2@in.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>,
habanero@linux.vnet.ibm.com,
Heiko Carstens <heiko.carstens@de.ibm.com>,
kvm@vger.kernel.org, lguest@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux390@de.ibm.com, netdev@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
steved@us.ibm.com, Tom Lendacky <tahm@linux.vnet.ibm.com>,
virtualization@lists.linux-foundation.org,
Shirley Ma <xma@us.ibm.com>
Subject: Re: [PATCH RFC 3/3] virtio_net: limit xmit polling
Date: Thu, 2 Jun 2011 18:44:31 +0300 [thread overview]
Message-ID: <20110602154431.GB11300@redhat.com> (raw)
In-Reply-To: <OFFF109303.D838CAE2-ON652578A3.0053357D-652578A3.00549366@in.ibm.com>
On Thu, Jun 02, 2011 at 08:56:42PM +0530, Krishna Kumar2 wrote:
> Return value in free_old_xmit() was wrong.
Could you check my latest RFC pls?
--
MST
prev parent reply other threads:[~2011-06-02 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 9:49 [PATCH RFC 0/3] virtio and vhost-net capacity handling Michael S. Tsirkin
2011-06-01 9:49 ` [PATCH RFC 1/3] virtio_ring: add capacity check API Michael S. Tsirkin
2011-06-02 2:11 ` Rusty Russell
2011-06-02 13:30 ` Michael S. Tsirkin
2011-06-01 9:49 ` [PATCH RFC 2/3] virtio_net: fix tx capacity checks using new API Michael S. Tsirkin
2011-06-02 2:10 ` Rusty Russell
2011-06-02 13:28 ` Michael S. Tsirkin
2011-06-01 9:50 ` [PATCH RFC 3/3] virtio_net: limit xmit polling Michael S. Tsirkin
2011-06-02 3:54 ` Rusty Russell
2011-06-02 13:34 ` Michael S. Tsirkin
2011-06-02 14:17 ` Krishna Kumar2
2011-06-02 14:43 ` Michael S. Tsirkin
2011-06-02 15:26 ` Krishna Kumar2
2011-06-02 15:34 ` Michael S. Tsirkin
2011-06-03 4:08 ` Krishna Kumar2
2011-06-02 15:44 ` Michael S. Tsirkin [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=20110602154431.GB11300@redhat.com \
--to=mst@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=habanero@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=lguest@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=steved@us.ibm.com \
--cc=tahm@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xma@us.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