All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@schaman.hu>
To: David Miller <davem@davemloft.net>
Cc: xen-devel@lists.xenproject.org, ian.campbell@citrix.com,
	wei.liu2@citrix.com, paul.durrant@citrix.com,
	linux@eikelenboom.it, netdev@vger.kernel.org,
	david.vrabel@citrix.com
Subject: Re: [PATCH net] xen-netback: Fix slot estimation
Date: Fri, 06 Jun 2014 11:20:45 +0100	[thread overview]
Message-ID: <539195FD.6080606@schaman.hu> (raw)
In-Reply-To: <20140605.150209.365488173138758921.davem@davemloft.net>

On 05/06/14 23:02, David Miller wrote:
> From: Zoltan Kiss<zoltan.kiss@citrix.com>
> Date: Tue, 3 Jun 2014 14:32:16 +0100
>
>> A recent commit (a02eb4 "xen-netback: worse-case estimate in xenvif_rx_action is
>> underestimating") capped the slot estimation to MAX_SKB_FRAGS, but that triggers
>> the next BUG_ON a few lines down, as the packet consumes more slots than
>> estimated.
>> This patch remove that cap, and if the frontend doesn't provide enough slot,
>> put back the skb to the top of the queue and caps rx_last_skb_slots. When the
>> next try also fails, it drops the packet.
>> Capping rx_last_skb_slots is needed because if the frontend never gives enough
>> slots, the ring gets stalled.
>>
>> Signed-off-by: Zoltan Kiss<zoltan.kiss@citrix.com>
> Like David Laight, I do not like this patch at all.
>
> Yes a crash or BUG_ON triggered is bad, but fixing it by deadlocking
> TCP connections (a silent failure) is not an improvement.
>
> I'm not applying this, sorry.
>
Hi,

I haven't wrote it explicitly, but my other patch "xen-netback: Fix 
handling of skbs requiring too many slots" supersedes this one.

  reply	other threads:[~2014-06-06 10:20 UTC|newest]

Thread overview: 16+ 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 13:37 ` Paul Durrant
2014-06-03 14:04   ` Zoltan Kiss
2014-06-03 14:04   ` Zoltan Kiss
2014-06-03 13:52 ` David Laight
2014-06-03 20:24   ` Zoltan Kiss
2014-06-03 20:24   ` Zoltan Kiss
2014-06-03 13:52 ` David Laight
2014-06-05 22:02 ` David Miller
2014-06-06 10:20   ` Zoltan Kiss [this message]
2014-06-06 20:06     ` David Miller
2014-06-06 20:06     ` David Miller
2014-06-06 10:20   ` Zoltan Kiss
2014-06-05 22:02 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2014-06-03 13:32 Zoltan Kiss

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=539195FD.6080606@schaman.hu \
    --to=zoltan.kiss@schaman.hu \
    --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 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.