From: Ottavio Campana <ottavio.campana@dei.unipd.it>
To: linux-kernel@vger.kernel.org
Subject: Oops when trying to create more than 16000 timers
Date: Mon, 15 Dec 2008 17:04:52 +0100 [thread overview]
Message-ID: <49468024.1020700@dei.unipd.it> (raw)
Hello,
I'm sorry if it is not the best place to ask, but I haven't find any answer.
I am currently developing a software that needs approx 60k timers. I
currently use timer_create and all the relative functions to manage timers.
I've noticed that after having created 16039 timers I always get an oops
from the kernel, which are always of the same kind:
Dec 15 15:20:00 evolution kernel: [601680.417064] BUG: unable to handle
kernel NULL pointer dereference at 0000000000000040 .
I tried looking at kernel/posix-timers.c and I discovered that posix
timers are kept in slab memory. By monitoring the my program I can see
that in /proc/slabinfo the number of timers increases till 16039, when I
get the oops and no more timers are created.
In /prob/slabinfo I have
posix_timers_cache 0 0 192 20 1 : tunables 120 60 8 : slabdata 0 0 0
If I try to increase tunables to 2400 120 16 the maximum number of posix
timers that I can create does not change.
How can I tune the kernel so that it supports 60k or more timers?
Thank for your help,
Ottavio
--
Ottavio Campana
Telecommunication Engineer
Lab. Immagini
Dept. of Information Engineering
University of Padova
Via Gradenigo 6/B
35131 Padova
Italy
phone: +39 049 8277641 fax: +39 049 8277699
e-mail: ottavio.campana@dei.unipd.it
next reply other threads:[~2008-12-15 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 16:04 Ottavio Campana [this message]
2008-12-15 16:45 ` Oops when trying to create more than 16000 timers Pekka Enberg
2008-12-15 21:41 ` Ottavio Campana
2008-12-15 21:37 ` Pekka Enberg
2008-12-15 22:46 ` Ottavio Campana
2008-12-15 21:44 ` Pekka Enberg
2008-12-16 23:18 ` Greg KH
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=49468024.1020700@dei.unipd.it \
--to=ottavio.campana@dei.unipd.it \
--cc=linux-kernel@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 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.