From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [BUG] 2.6.37-rc5 Memory leak in net/ipv4/udp.c
Date: Fri, 17 Dec 2010 15:28:12 +0100 [thread overview]
Message-ID: <19723.29564.671887.636356@ipc1.ka-ro> (raw)
In-Reply-To: <1292595727.2906.14.camel@edumazet-laptop>
Hi,
Eric Dumazet writes:
> Le vendredi 17 décembre 2010 à 12:56 +0100, Lothar Waßmann a écrit :
>
> > Forget about this. I was a little confused when reading the
> > alloc_large_system_hash() function. No I understand.
>
> Any idea why you got a small allocation ?
>
How much should I expect?
> How much LOWMEM do you have on your platform ?
>
It's a new platform with a Freescale i.MX28 SoC:
Linux version 2.6.37-rc5-karo+ (lothar@ipc1) (gcc version 4.4.1 (GCC) ) #43 PREEMPT Fri Dec 17 13:59:40 CET 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Ka-Ro electronics TX28 module
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat c0454c9c, node_mem_map c0994000
Normal zone: 288 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 32480 pages, LIFO batch:7
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32480
Kernel command line: init=/linuxrc tx28_baseboard=stk5-v3 root=/dev/nfs nfsroot=192.168.1.225:/tftpboot/KARO/imx28,nolock ip=bootp debug panic=1 console=ttyAM0,115200 ro
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 119968k/119968k available, 11104k reserved, 0K highmem
Lothar Waßmann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Geschäftsführer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info@karo-electronics.de
___________________________________________________________
prev parent reply other threads:[~2010-12-17 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 10:18 [BUG] 2.6.37-rc5 Memory leak in net/ipv4/udp.c Lothar Waßmann
2010-12-17 10:35 ` Eric Dumazet
2010-12-17 11:11 ` Lothar Waßmann
2010-12-17 11:32 ` Eric Dumazet
2010-12-17 11:47 ` Lothar Waßmann
2010-12-17 11:56 ` Lothar Waßmann
2010-12-17 14:22 ` Eric Dumazet
2010-12-17 14:28 ` Lothar Waßmann [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=19723.29564.671887.636356@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--cc=eric.dumazet@gmail.com \
--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