Prev: vhost: fix barrier pairing
Next: [PATCH] rwsem: Test for no active locks in __rwsem_do_wake undo code
From: Tvrtko Ursulin on 12 May 2010 06:30

Hi all,

As the subject says, is this a know issue? I have been tracking the growth at
one second intervals and it looks like this:

512 (67716608) Slab: 606744 kB
512 (67717120) Slab: 606752 kB
512 (67717632) Slab: 606756 kB
0 (67718144) Slab: 606756 kB
512 (67718144) Slab: 606760 kB
1024 (67718656) Slab: 606768 kB
512 (67719680) Slab: 606772 kB
512 (67720192) Slab: 606776 kB
0 (67720704) Slab: 606776 kB
512 (67720704) Slab: 606780 kB

First fiels is the diff in numobj, in parentheses is actual numobj and last is
the total slab size from /proc/meminfo.

kmalloc-8 68044800 68044800 8 512 1 : tunables 0 0 0
: slabdata 132900 132900 0

dm-io slab also seems large, don't know... :
dm_io 75924 147288 40 102 1 : tunables 0 0 0 :
slabdata 1444 1444 0

Some other info about the system/kernel is attached.

Tvrtko



Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
From: Tvrtko Ursulin on 12 May 2010 06:40
On Wednesday 12 May 2010 11:21:48 Tvrtko Ursulin wrote:
> Hi all,
>
> As the subject says, is this a know issue? I have been tracking the growth
> at one second intervals and it looks like this:
>
> 512 (67716608) Slab: 606744 kB
> 512 (67717120) Slab: 606752 kB
> 512 (67717632) Slab: 606756 kB
> 0 (67718144) Slab: 606756 kB
> 512 (67718144) Slab: 606760 kB
> 1024 (67718656) Slab: 606768 kB
> 512 (67719680) Slab: 606772 kB
> 512 (67720192) Slab: 606776 kB
> 0 (67720704) Slab: 606776 kB
> 512 (67720704) Slab: 606780 kB
>
> First fiels is the diff in numobj, in parentheses is actual numobj and last
> is the total slab size from /proc/meminfo.
>
> kmalloc-8 68044800 68044800 8 512 1 : tunables 0 0
> 0
>
> : slabdata 132900 132900 0
>
> dm-io slab also seems large, don't know... :
> dm_io 75924 147288 40 102 1 : tunables 0 0 0
> : slabdata 1444 1444 0
>
> Some other info about the system/kernel is attached.

I think it is DRM (radeon) related, leak stopped when I closed all X programs.
I am compiling 2.6.33.3 right now and will soon reboot into it.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Tvrtko Ursulin on 12 May 2010 07:00
On Wednesday 12 May 2010 11:38:05 Tvrtko Ursulin wrote:

[snip]
> I think it is DRM (radeon) related, leak stopped when I closed all X
> programs. I am compiling 2.6.33.3 right now and will soon reboot into it.

Leak is still present in 2.6.33.3 - the more GUI activity the more it leaks.
So the ~512 objects per second was with xosview running, but moving windows or
browsing through menus can leak a lot more (per second).

Is version of userspace drm library interesting? It is 2.4.20
(libdrm-2.4.20-12.1.x86_64).

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Pekka Enberg on 12 May 2010 09:10
Hi Tvrtko,

On Wed, May 12, 2010 at 1:21 PM, Tvrtko Ursulin
<tvrtko.ursulin(a)sophos.com> wrote:
> As the subject says, is this a know issue? I have been tracking the growth at
> one second intervals and it looks like this:
>
> 512 (67716608) Slab: � � � � � � 606744 kB
> 512 (67717120) Slab: � � � � � � 606752 kB
> 512 (67717632) Slab: � � � � � � 606756 kB
> 0 (67718144) Slab: � � � � � � 606756 kB
> 512 (67718144) Slab: � � � � � � 606760 kB
> 1024 (67718656) Slab: � � � � � � 606768 kB
> 512 (67719680) Slab: � � � � � � 606772 kB
> 512 (67720192) Slab: � � � � � � 606776 kB
> 0 (67720704) Slab: � � � � � � 606776 kB
> 512 (67720704) Slab: � � � � � � 606780 kB
>
> First fiels is the diff in numobj, in parentheses is actual numobj and last is
> the total slab size from /proc/meminfo.
>
> kmalloc-8 � � � � 68044800 68044800 � � �8 �512 � �1 : tunables � �0 � �0 � �0
> : slabdata 132900 132900 � � �0
>
> dm-io slab also seems large, don't know... :
> dm_io � � � � � � �75924 147288 � � 40 �102 � �1 : tunables � �0 � �0 � �0 :
> slabdata � 1444 � 1444 � � �0
>
> Some other info about the system/kernel is attached.

[snip]

You might want to try out the built-in kernel memory leak detector.
See Documentation/kmemleak.txt for details how to enable it and use
it.

Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Tvrtko Ursulin on 12 May 2010 09:10
On Wednesday 12 May 2010 14:00:51 Pekka Enberg wrote:
> [snip]
>
> You might want to try out the built-in kernel memory leak detector.
> See Documentation/kmemleak.txt for details how to enable it and use
> it.

Thanks for the suggestion, I will have to try it out once but not this time :)
because 2.6.34-rc7 seems to be fine, or in other words not leaking.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 |  Next  |  Last
Pages: 1 2 3
Prev: vhost: fix barrier pairing
Next: [PATCH] rwsem: Test for no active locks in __rwsem_do_wake undo code