From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: David Laight <David.Laight@ACULAB.COM>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"paul.durrant@citrix.com" <paul.durrant@citrix.com>,
"linux@eikelenboom.it" <linux@eikelenboom.it>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"david.vrabel@citrix.com" <david.vrabel@citrix.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH net] xen-netback: Fix slot estimation
Date: Tue, 3 Jun 2014 21:24:31 +0100 [thread overview]
Message-ID: <538E2EFF.7000103@citrix.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1725674B@AcuExch.aculab.com>
On 03/06/14 14:52, David Laight wrote:
> From: netdev-owner@vger.kernel.org
>> @@ -615,9 +608,27 @@ static void xenvif_rx_action(struct xenvif *vif)
>>
>> /* If the skb may not fit then bail out now */
>> if (!xenvif_rx_ring_slots_available(vif, max_slots_needed)) {
>> + /* If the skb needs more than MAX_SKB_FRAGS slots, it
>> + * can happen that the frontend never gives us enough.
>> + * To avoid spining on that packet, first we put it back
>> + * to the top of the queue, but if the next try fail,
>> + * we drop it.
>> + */
>> + if (max_slots_needed > MAX_SKB_FRAGS &&
>> + vif->rx_last_skb_slots == MAX_SKB_FRAGS) {
>> + kfree_skb(skb);
>> + vif->rx_last_skb_slots = 0;
>> + continue;
>> + }
>
> A silent discard here doesn't seem right at all.
> While it stops the kernel crashing, or the entire interface locking
> up; it is likely to leave one connection 'stuck' - a TCP retransmission
> is likely to include the same fragments.
> From a user point of view this as almost as bad.
Yes, we are aware of this problem for a while. However I have an idea to
solve that in a way that we don't lose performance, and these packets
can pass through as well. See my patch called "Fix handling of skbs
requiring too many slots"
Zoli
next prev parent reply other threads:[~2014-06-03 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 13:32 [PATCH net] xen-netback: Fix slot estimation Zoltan Kiss
2014-06-03 13:37 ` Paul Durrant
2014-06-03 14:04 ` Zoltan Kiss
2014-06-03 13:52 ` David Laight
2014-06-03 20:24 ` Zoltan Kiss [this message]
2014-06-05 22:02 ` David Miller
2014-06-06 10:20 ` Zoltan Kiss
2014-06-06 20:06 ` 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=538E2EFF.7000103@citrix.com \
--to=zoltan.kiss@citrix.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=linux@eikelenboom.it \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--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).