From: Artem Bityutskiy <dedekind@infradead.org>
To: John.Smith@pace.com
Cc: linux-mtd@lists.infradead.org
Subject: RE: UBI memory leak after creating and removing volumes
Date: Tue, 17 Feb 2009 17:24:19 +0200 [thread overview]
Message-ID: <1234884259.17790.271.camel@localhost.localdomain> (raw)
In-Reply-To: <F21E92E7B38A1F4D9211341290F7569807EED247@salexc1.pace.internal>
On Tue, 2009-02-17 at 14:33 +0000, John.Smith@pace.com wrote:
> After 0, 1000 and 2000 iterations of a test of creating 2 UBI volumes,
> then removing them, /proc/slab_allocators shows these three items
> obviously increasing:
>
> inode_cache: 327 alloc_inode+0x140/0x148
> inode_cache: 3329 alloc_inode+0x140/0x148
> inode_cache: 6329 alloc_inode+0x140/0x148
> (3 objects per iteration)
>
> sysfs_dir_cache: 1402 sysfs_new_dirent+0x2c/0xa0
> sysfs_dir_cache: 15402 sysfs_new_dirent+0x2c/0xa0
> sysfs_dir_cache: 29402 sysfs_new_dirent+0x2c/0xa0
> (14 objects per iteration)
>
> dentry_cache: 669 d_alloc+0x30/0x214
> dentry_cache: 3823 d_alloc+0x30/0x214
> dentry_cache: 6823 d_alloc+0x30/0x214
> (3 objects per iteration)
Hmm, may be this is related to sysfs? Every time you create or delete
a volume UBIFS creates/deletes sysfs entries. May be some are forgotten,
or it messes up kobject refcounting, so the kobjects are never released.
> I don't know how to track these things down fully. But I
> believe they relate to the elevator queue.
Hmm? Sorry, did not realize how elevator may be involved into
UBI volume creation/deletion. You mean when we create a volume,
userspace udev is called, and creates device node on your host
FS, which involves elevators? You can try disabling udev then.
Anyway, too late, I have to go home ow.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-02-17 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 14:33 UBI memory leak after creating and removing volumes John.Smith
2009-02-17 15:24 ` Artem Bityutskiy [this message]
2009-02-17 15:24 ` Artem Bityutskiy
2009-02-17 22:02 ` John Smith
2009-02-17 15:39 ` Artem Bityutskiy
2009-02-21 21:30 ` John Smith
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 12:01 John.Smith
2009-02-17 12:23 ` Artem Bityutskiy
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=1234884259.17790.271.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=John.Smith@pace.com \
--cc=linux-mtd@lists.infradead.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.