From: Kevin Wolf <kwolf@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jes.Sorensen@redhat.com,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] e1000: check buffer availability
Date: Mon, 28 Mar 2011 13:37:55 +0200 [thread overview]
Message-ID: <4D907313.20409@redhat.com> (raw)
In-Reply-To: <20110327150156.GA7975@redhat.com>
Am 27.03.2011 17:01, schrieb Michael S. Tsirkin:
> Reduce spurious packet drops on RX ring empty
> by verifying that we have at least 1 buffer
> ahead of the time.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Acked-by: Kevin Wolf <kwolf@redhat.com>
prev parent reply other threads:[~2011-03-28 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 15:01 [Qemu-devel] [PATCH] e1000: check buffer availability Michael S. Tsirkin
2011-03-28 10:50 ` [Qemu-devel] " Juan Quintela
2011-03-28 11:37 ` Kevin Wolf [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=4D907313.20409@redhat.com \
--to=kwolf@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).