From: Andi Kleen <ak@muc.de>
To: Rogier Wolff <R.E.Wolff@bitwizard.nl>
Cc: Ingo Molnar <mingo@chiara.csoma.elte.hu>,
"William J. Earl" <wje@cthulhu.engr.sgi.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel List <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org
Subject: Re: Getting big areas of memory, in 2.3.x?
Date: Fri, 10 Dec 1999 00:46:34 +0100 [thread overview]
Message-ID: <19991210004634.A3013@fred.muc.de> (raw)
In-Reply-To: <199912092332.AAA27593@cave.bitwizard.nl>; from Rogier Wolff on Fri, Dec 10, 1999 at 12:32:01AM +0100
On Fri, Dec 10, 1999 at 12:32:01AM +0100, Rogier Wolff wrote:
> Ingo Molnar wrote:
> > yep, if eg. an fsck happened before modules are loaded then RAM is filled
> > up with the buffer-cache. The best guarantee is to compile such drivers
> > into the kernel.
>
> My ISDN drivers don't start up correctly after an fsck.
This is a known bug in the isdn driver. They use a >64K array for their
device structures. The easy fix is to just replace the kmalloc with a
vmalloc() [the better fix would be to use a array of pointers and allocate
the device structures only when needed]. These are just internal structures
that are never touched by hardware, so vmalloc is fine.
I believe Karsten has fixed it in the latest I4L Tree.
-Andi
---
This is like TV. I don't like TV.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-12-09 23:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 1:03 Getting big areas of memory, in 2.3.x? Jeff Garzik
1999-12-09 2:28 ` Alan Cox
1999-12-09 2:45 ` Jeff Garzik
1999-12-09 5:22 ` Oliver Xymoron
1999-12-09 12:25 ` Ingo Molnar
1999-12-09 20:24 ` Jeff Garzik
1999-12-09 20:31 ` Kanoj Sarcar
1999-12-09 20:39 ` Rik van Riel
1999-12-09 20:54 ` Kanoj Sarcar
1999-12-09 23:21 ` Ingo Molnar
1999-12-09 22:27 ` Kanoj Sarcar
1999-12-09 23:16 ` Ingo Molnar
1999-12-09 23:09 ` Benjamin C.R. LaHaise
1999-12-10 0:44 ` Ingo Molnar
1999-12-10 0:18 ` William J. Earl
1999-12-11 19:56 ` Stephen C. Tweedie
1999-12-10 12:21 ` Rik van Riel
1999-12-10 13:42 ` Ingo Molnar
1999-12-10 18:04 ` William J. Earl
1999-12-09 20:50 ` William J. Earl
1999-12-09 23:15 ` Ingo Molnar
1999-12-09 22:13 ` William J. Earl
1999-12-09 22:26 ` Alan Cox
1999-12-09 23:42 ` William J. Earl
1999-12-09 23:50 ` Alan Cox
1999-12-10 0:30 ` William J. Earl
1999-12-10 0:37 ` Alan Cox
1999-12-10 4:19 ` Oliver Xymoron
1999-12-10 10:14 ` Thomas Sailer
1999-12-09 23:24 ` Ingo Molnar
1999-12-09 22:33 ` Jeff Garzik
1999-12-09 23:32 ` Rogier Wolff
1999-12-09 23:44 ` JF Martinez
1999-12-10 0:52 ` Ingo Molnar
1999-12-09 23:46 ` Andi Kleen [this message]
1999-12-10 13:52 ` Stephen C. Tweedie
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=19991210004634.A3013@fred.muc.de \
--to=ak@muc.de \
--cc=R.E.Wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=wje@cthulhu.engr.sgi.com \
/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.