From: Andi Kleen <andi@firstfloor.org>
To: Ivan Dichev <idichev@obs.bg>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
netdev@vger.kernel.org
Subject: Re: Slow OOM in netif_RX function
Date: Mon, 4 Feb 2008 16:55:26 +0100 [thread overview]
Message-ID: <20080204155526.GA7988@one.firstfloor.org> (raw)
In-Reply-To: <47A72740.9030706@obs.bg>
> Nothing that looks like a struct net_device. All the dumped leaked slab
> look the same until "45 20 05 d8" (the ascii 'E' on the 3rd line).
45 ... is often the start of an IP header (IPv4, 5*4=20 bytes length)
You could dump them to a file (e.g. using a sial script) and then
look at them with tcpdump or similar to get an idea what kinds
of packets they are.
-Andi
next prev parent reply other threads:[~2008-02-04 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 17:28 Slow OOM in netif_RX function Ivan Dichev
2008-01-24 18:29 ` Stephen Hemminger
2008-01-24 19:12 ` Eric Dumazet
2008-01-24 21:18 ` Ivan H. Dichev
2008-01-24 21:51 ` Francois Romieu
2008-01-25 13:21 ` Andi Kleen
2008-01-25 14:12 ` Arnaldo Carvalho de Melo
2008-02-01 12:51 ` Ivan Dichev
2008-02-01 13:16 ` Eric Dumazet
2008-02-01 15:38 ` Ivan Dichev
2008-02-04 14:54 ` Ivan Dichev
2008-02-04 15:55 ` Andi Kleen [this message]
2008-02-05 9:04 ` Ivan Mitev
2008-02-01 14:29 ` 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=20080204155526.GA7988@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=dada1@cosmosbay.com \
--cc=idichev@obs.bg \
--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 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).