From: Jeremy Fitzhardinge <jeremy@goop.org>
To: David Miller <davem@davemloft.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"Xu, Dongxiao" <dongxiao.xu@intel.com>
Subject: [GIT PULL] xen-netfront driver updates for 2.6.36
Date: Tue, 03 Aug 2010 11:11:20 -0700 [thread overview]
Message-ID: <4C585BC8.5070203@goop.org> (raw)
Hi Dave,
Here's a git branch with some updates to the Xen netfront driver, which
add a new "smartpoll" mode to the netfront backend protocol, which is
basically equivalent to interrupt mitigation. They've been in
linux-next for a week or so.
Do you want to take this via the net tree, or are you OK with me
submitting them directly?
Thanks,
J
The following changes since commit 74fca6a42863ffacaf7ba6f1936a9f228950f657:
Linux 2.6.31 (2009-09-09 15:13:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/netfront
Dongxiao Xu (1):
xen/netfront: Use smart polling instead of event notification.
Ian Campbell (2):
xen/rings: make protocol specific usage of shared sring explicit
xen/netfront: make protocol specific usage of shared sring explicit
drivers/net/xen-netfront.c | 114 ++++++++++++++++++++++++++++++++++++++-
include/xen/interface/io/ring.h | 11 ++++-
2 files changed, 122 insertions(+), 3 deletions(-)
next reply other threads:[~2010-08-03 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 18:11 Jeremy Fitzhardinge [this message]
2010-08-03 18:12 ` [GIT PULL] xen-netfront driver updates for 2.6.36 Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2010-08-03 18:39 Jeremy Fitzhardinge
2010-08-03 23:37 ` David Miller
2010-08-04 0:49 ` Jeremy Fitzhardinge
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=4C585BC8.5070203@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=davem@davemloft.net \
--cc=dongxiao.xu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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.