From: Imran.Patel@nokia.com
To: ak@suse.de, Imran.Patel@nokia.com
Cc: netfilter-devel@us5.samba.org, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: RE: skb allocation problems
Date: Tue, 10 Apr 2001 19:27:29 +0300 [thread overview]
Message-ID: <2D6CADE9B0C6D411A27500508BB3CBD063CF0D@eseis15nok> (raw)
> On Mon, Apr 09, 2001 at 07:03:46PM +0300, Imran.Patel@nokia.com wrote:
> > I have written a test module which closely mirrors what my
> code tries to
> > do(attached below). This is what i get:
> >
> > PRE_R: old skb:c371ee40 new skb:c371ee30
>
> I guess oldskb->len is <=0xc, and the slab allocator packs
> them near together
> in the same zone.
nope. i have checked it, the length of the older skb is perfectly ok.....and
i even found that this weird behaviour happens only when the old skb buffer
length is between 80 and 224 bytes.
and apart from this problem, i even found out that when i send a packet >=
186 bytes the kernel allocates a lot of memory in the skb...the output from
a simple test module is below:
PRE_R: skb: c7aa0da0 skblen: 185 headroom: 32 tailroom: 7 total_len: 224
PRE_R: skb: c7a43020 skblen: 186 headroom: 32 tailroom: 1334 total_len: 1552
This was generated by sending ipv4 ping packets of different sizes...I
tested it using 2.4.1 and 2.4.3 on two machines (both dual stack).
What the hell's going on :( ???
imran
next reply other threads:[~2001-04-10 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 16:27 Imran.Patel [this message]
2001-04-10 17:23 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-04-09 16:03 Imran.Patel
2001-04-10 6:07 ` Andi Kleen
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=2D6CADE9B0C6D411A27500508BB3CBD063CF0D@eseis15nok \
--to=imran.patel@nokia.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@us5.samba.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
all inboxes | Powered by JetHome®