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 handling of skbs requiring too many slots
Date: Wed, 4 Jun 2014 16:53:18 +0100 [thread overview]
Message-ID: <538F40EE.2040609@citrix.com> (raw)
In-Reply-To: <538EF1B3.40904@citrix.com>
On 04/06/14 11:15, Zoltan Kiss wrote:
> On 04/06/14 09:50, David Laight wrote:
>> From: netdev-owner@vger.kernel.org
>>> 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 introduces full_coalesce on the skb callback buffer, which
>>> is used in
>>> start_new_rx_buffer() to decide whether netback needs coalescing more
>>> aggresively. By doing that, no packet should need more than
>>> XEN_NETIF_MAX_TX_SIZE / PAGE_SIZE data slots, as the provided buffers
>>> are fully
>>> utilized.
>> ...
>>> -static bool start_new_rx_buffer(int offset, unsigned long size, int
>>> head)
>>> +static bool start_new_rx_buffer(int offset,
>>> + unsigned long size,
>>> + int head,
>>> + bool full_coalesce)
>>
>> The above is completely incorrect layout ...
> Can you elaborate a bit please on "above"?
I just realized you're not talking about skb layout but format. I'll fix
that.
Zoli
next prev parent reply other threads:[~2014-06-04 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 20:30 [PATCH net] xen-netback: Fix handling of skbs requiring too many slots Zoltan Kiss
2014-06-04 8:50 ` David Laight
2014-06-04 10:15 ` Zoltan Kiss
2014-06-04 15:53 ` Zoltan Kiss [this message]
2014-06-04 15:09 ` annie li
2014-06-04 15:42 ` [Xen-devel] " Zoltan Kiss
2014-06-04 15:59 ` annie li
2014-06-11 12:36 ` Zoltan Kiss
2014-06-11 19: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=538F40EE.2040609@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).