From: David Miller <davem@davemloft.net>
To: david.vrabel@citrix.com
Cc: netdev@vger.kernel.org, xen-devel@lists.xenproject.org,
ian.campbell@citrix.com, wei.liu2@citrix.com
Subject: Re: [PATCHv1 net] xen-netback: require fewer guest Rx slots when not using GSO
Date: Wed, 09 Sep 2015 12:34:59 -0700 (PDT) [thread overview]
Message-ID: <20150909.123459.1956039261743477106.davem@davemloft.net> (raw)
In-Reply-To: <1441718714-3256-1-git-send-email-david.vrabel@citrix.com>
From: David Vrabel <david.vrabel@citrix.com>
Date: Tue, 8 Sep 2015 14:25:14 +0100
> Commit f48da8b14d04ca87ffcffe68829afd45f926ec6a (xen-netback: fix
> unlimited guest Rx internal queue and carrier flapping) introduced a
> regression.
>
> The PV frontend in IPXE only places 4 requests on the guest Rx ring.
> Since netback required at least (MAX_SKB_FRAGS + 1) slots, IPXE could
> not receive any packets.
>
> a) If GSO is not enabled on the VIF, fewer guest Rx slots are required
> for the largest possible packet. Calculate the required slots
> based on the maximum GSO size or the MTU.
>
> This calculation of the number of required slots relies on
> 1650d5455bd2 (xen-netback: always fully coalesce guest Rx packets)
> which present in 4.0-rc1 and later.
>
> b) Reduce the Rx stall detection to checking for at least one
> available Rx request. This is fine since we're predominately
> concerned with detecting interfaces which are down and thus have
> zero available Rx requests.
>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Applied, thanks David.
next prev parent reply other threads:[~2015-09-09 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 13:25 [PATCHv1 net] xen-netback: require fewer guest Rx slots when not using GSO David Vrabel
2015-09-09 10:41 ` Wei Liu
2015-09-09 19:34 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-09-10 9:41 ` David Vrabel
2015-09-09 19:34 ` David Miller [this message]
2015-09-15 10:30 ` David Vrabel
2015-09-15 17:15 ` 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=20150909.123459.1956039261743477106.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=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).