From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shlomo Pongartz <shlomop@mellanox.com>
Cc: Or Gerlitz <ogerlitz@mellanox.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Erez Shitrit <erezsh@mellanox.com>
Subject: Re: getting warn once around skb_try_coalesce
Date: Tue, 10 Jul 2012 15:01:47 +0200 [thread overview]
Message-ID: <1341925307.3265.5087.camel@edumazet-glaptop> (raw)
In-Reply-To: <4FFC2191.1040001@mellanox.com>
On Tue, 2012-07-10 at 15:35 +0300, Shlomo Pongartz wrote:
> I've applied the patch and there are no more warnings. Thanks.
> Can you please elaborate on this issue which was there from day one and
> AFAIK never manifested itself.
two problems :
1) truesize underestimation
Well, I posted at least 50 patches related to various skb->truesize
mismatches in the past year.
skb->truesize is/should_be the true size of skb, that is the memory
allocated for sk_buff, skb->head and all fragments
Check commit e1ac50f64691de9a (bnx2x: fix skb truesize underestimation)
for a similar fix done on bnx2x
Its very important to do so to avoid OOM.
If you account few bytes per fragment but allocate PAGE_SIZE bytes, its
pretty easy to allocate far more memory than allowed by various
socket/tcp/udp/... limits, and exhaust kernel memory.
commit 924a4c7d2e962b (myri10ge: fix truesize underestimation)
commit 7b8b59617ead5acc (igbvf: fix truesize underestimation)
I probably missed your driver because it was not on drivers/net tree but
drivers/infiniband
2) Not enough tailroom
Invisible but performance suffers, because IP/TCP will need
to call pskb_may_pull() and the expensive __pskb_pull_tail().
So each incoming IP packet needs at least one pskb_expand_head().
I'll send an official patch, but I believe I should refine the tailroom
allocation like that :
diff --git a/drivers/infiniband/ulp/ipoib/ipoib_ib.c b/drivers/infiniband/ulp/ipoib/ipoib_ib.c
index 5c1bc99..f10221f 100644
--- a/drivers/infiniband/ulp/ipoib/ipoib_ib.c
+++ b/drivers/infiniband/ulp/ipoib/ipoib_ib.c
@@ -123,7 +123,7 @@ static void ipoib_ud_skb_put_frags(struct ipoib_dev_priv *priv,
skb_frag_size_set(frag, size);
skb->data_len += size;
- skb->truesize += size;
+ skb->truesize += PAGE_SIZE;
} else
skb_put(skb, length);
@@ -156,14 +156,18 @@ static struct sk_buff *ipoib_alloc_rx_skb(struct net_device *dev, int id)
struct ipoib_dev_priv *priv = netdev_priv(dev);
struct sk_buff *skb;
int buf_size;
+ int tailroom;
u64 *mapping;
- if (ipoib_ud_need_sg(priv->max_ib_mtu))
+ if (ipoib_ud_need_sg(priv->max_ib_mtu)) {
buf_size = IPOIB_UD_HEAD_SIZE;
- else
+ tailroom = 128; /* reserve some tailroom for IP/TCP headers */
+ } else {
buf_size = IPOIB_UD_BUF_SIZE(priv->max_ib_mtu);
+ tailroom = 0;
+ }
- skb = dev_alloc_skb(buf_size + 4);
+ skb = dev_alloc_skb(buf_size + tailroom + 4);
if (unlikely(!skb))
return NULL;
prev parent reply other threads:[~2012-07-10 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 9:54 getting warn once around skb_try_coalesce Or Gerlitz
2012-07-10 10:18 ` Eric Dumazet
2012-07-10 11:14 ` Eric Dumazet
2012-07-10 11:22 ` Eric Dumazet
2012-07-10 12:19 ` Or Gerlitz
2012-07-10 12:35 ` Shlomo Pongartz
2012-07-10 13:01 ` Eric Dumazet [this message]
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=1341925307.3265.5087.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=erezsh@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=shlomop@mellanox.com \
/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