From: Eric Dumazet <eric.dumazet@gmail.com>
To: monstr@monstr.eu
Cc: David Miller <davem@davemloft.net>,
John Williams <john.williams@petalogix.com>,
netdev@vger.kernel.org
Subject: Re: ICMP packets - ll_temac with Microblaze
Date: Wed, 21 Dec 2011 12:05:55 +0100 [thread overview]
Message-ID: <1324465555.2728.32.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <4EF1BAE1.7020409@monstr.eu>
Le mercredi 21 décembre 2011 à 11:54 +0100, Michal Simek a écrit :
> Eric Dumazet wrote:
> > Le mercredi 21 décembre 2011 à 11:41 +0100, Michal Simek a écrit :
> >
> >> yes, page size is 4k.
> >>
> >> Here is the log for allocation - origin size for MTU 9000 is 0x2420(9248) and size after
> >> overhead is 0x3f40(16192)
> >>
> >> kmalloc_node_track_caller size 00002420, SKB_WITH_OVERHEAD(ksize(data)) 00003f40
> >> skb->head c7870000
> >> skb->data c7870000
> >> skb->tail c7870000
> >> skb->truesize 000040c0
> >> skb->end c7873f40
> >>
> >
> > So basically truesize is bigger than previous kernel, and you hit a
> > socket limit. (RCVBUF ?)
>
> Where is that limit setup?
>
Might be in the application itself.
setsockopt(socket, SOL_SOCKET, SO_RCVBUF, &limit, sizeof(limit));
kernel currently apply a factor of two to take into account skb
overhead. This might be not enough with jumbo frames.
next prev parent reply other threads:[~2011-12-21 11:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 10:11 ICMP packets - ll_temac with Microblaze Michal Simek
2011-12-21 10:28 ` Eric Dumazet
2011-12-21 10:30 ` Michal Simek
2011-12-21 10:30 ` Eric Dumazet
2011-12-21 10:32 ` Michal Simek
2011-12-21 10:37 ` Eric Dumazet
2011-12-21 10:41 ` Michal Simek
2011-12-21 10:45 ` Eric Dumazet
2011-12-21 10:54 ` Michal Simek
2011-12-21 11:05 ` Eric Dumazet [this message]
2011-12-21 11:03 ` Eric Dumazet
2011-12-21 11:10 ` Michal Simek
2011-12-21 11:13 ` Eric Dumazet
2011-12-21 11:50 ` Michal Simek
2011-12-21 12:39 ` Eric Dumazet
2011-12-21 13:28 ` Michal Simek
2011-12-21 13:40 ` Eric Dumazet
2011-12-21 14:24 ` Michal Simek
2011-12-21 15:30 ` Eric Dumazet
2011-12-21 15:44 ` Eric Dumazet
2011-12-21 16:01 ` Jun Zhao
2011-12-21 16:05 ` Eric Dumazet
2011-12-21 16:11 ` Jun Zhao
2011-12-21 16:39 ` David Laight
2011-12-21 16:50 ` Eric Dumazet
2011-12-21 15:59 ` Eric Dumazet
2011-12-21 17:11 ` Eric Dumazet
2011-12-21 20:55 ` David Miller
2011-12-22 7:49 ` Michal Simek
2011-12-22 7:57 ` Eric Dumazet
2011-12-22 8:05 ` Michal Simek
2011-12-22 10:32 ` Michael Wang
2011-12-22 10:46 ` Eric Dumazet
2011-12-22 13:01 ` Michael Wang
2011-12-22 13:21 ` Eric Dumazet
2011-12-22 13:42 ` Michael Wang
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=1324465555.2728.32.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=john.williams@petalogix.com \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.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.