From: David Vrabel <david.vrabel@citrix.com>
To: <netdev@vger.kernel.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
<xen-devel@lists.xenproject.org>,
Ian Campbell <ian.campbell@citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: [PATCHv1 0/3 net-next] xen-netback: guest Rx queue drain and stall fixes
Date: Wed, 22 Oct 2014 14:08:52 +0100 [thread overview]
Message-ID: <1413983335-8307-1-git-send-email-david.vrabel@citrix.com> (raw)
This series fixes two critical xen-netback bugs.
1. Netback may consume all of host memory by queuing an unlimited
number of skb on the internal guest Rx queue. This behaviour is
guest triggerable.
2. Carrier flapping under high traffic rates which reduces
performance.
The first patch is a prerequite. Removing support for frontends with
feature-rx-notify makes it easier to reason about the correctness of
netback since it no longer has to support this outdated and broken
mode.
David
next reply other threads:[~2014-10-22 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:08 David Vrabel [this message]
2014-10-22 13:08 ` [PATCH 1/3] xen-netback: make feature-rx-notify mandatory David Vrabel
2014-10-23 11:16 ` Wei Liu
2014-10-23 11:32 ` Wei Liu
2014-10-23 11:37 ` David Vrabel
2014-10-23 11:44 ` Wei Liu
2014-10-23 11:52 ` David Vrabel
2014-10-22 13:08 ` [PATCH 2/3] xen-netback: fix unlimited guest Rx internal queue and carrier flapping David Vrabel
2014-10-23 11:40 ` Wei Liu
2014-10-22 13:08 ` [PATCH 3/3] xen-netback: reintroduce guest Rx stall detection David Vrabel
2014-10-23 11:49 ` Wei Liu
2014-10-25 18:14 ` [PATCHv1 0/3 net-next] xen-netback: guest Rx queue drain and stall fixes David Miller
2014-10-25 18:17 ` 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=1413983335-8307-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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).