From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [BUG] vmalloc, kmalloc - 2.4.x
Date: 03 Feb 2003 15:13:42 +0000 [thread overview]
Message-ID: <1044285222.2396.14.camel@gregs> (raw)
few days ago i started to port driver for our hardware in company from
windows to linux. It is simple ISA card, which gives me interrupt each
8ms. So i can check it state and latch some sort of watchdog on it -
saying that i am still running (just for security, if system hangs card
is blocking all inputs/outputs).
But anyway, i was collecting all data from the card in dynamically
allocated memory. This gives me at least 300 * 20 bytes allocated. i
have sigle small allocation running on each interrupt.
Driver is working fine under win2k even if i collect as much as 10000
allocations, afterwards system uses loads of processor.
Linux (2.4.19 ,2.4.20, 2.4.21-pre[1,2,3,4] i tried so far) gives me oups
arount 80th allocation.
>From http://hit-six.co.uk/~gj/testmod.tar.bz2 you can download simple
module that shows what happends. But be carefull, it oupses very fast !
system is running up2dated Debian(stable), and i am using gcc version:
gcc version 2.95.4 20011002
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 Labs
next reply other threads:[~2003-02-03 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 15:13 Grzegorz Jaskiewicz [this message]
2003-02-03 15:19 ` [BUG] vmalloc, kmalloc - 2.4.x Oliver Neukum
2003-02-03 15:19 ` Arjan van de Ven
2003-02-03 15:35 ` Grzegorz Jaskiewicz
2003-02-03 15:35 ` Arjan van de Ven
2003-02-03 22:52 ` David Woodhouse
2003-02-03 15:22 ` Arjan van de Ven
2003-02-03 15:42 ` Grzegorz Jaskiewicz
2003-02-03 15:52 ` Russell King
2003-02-03 15:58 ` Arnaldo Carvalho de Melo
2003-02-03 16:07 ` Grzegorz Jaskiewicz
2003-02-03 15:39 ` Richard B. Johnson
[not found] <1044284924.2402.12.camel@gregs>
[not found] ` <1044289102.21009.1.camel@irongate.swansea.linux.org.uk>
2003-02-03 15:40 ` Grzegorz Jaskiewicz
2003-02-03 15:40 ` Grzegorz Jaskiewicz
2003-02-03 17:02 ` Benjamin Herrenschmidt
2003-02-03 17:18 ` Alan Cox
2003-02-03 22:54 ` David Woodhouse
2003-02-04 9:35 ` Arjan van de Ven
2003-02-04 12:33 ` Dave Jones
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=1044285222.2396.14.camel@gregs \
--to=gj@pointblue.com.pl \
--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.