From: Stephan von Krawczynski <skraw@ithnet.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Memory problem with bttv driver
Date: Tue, 15 Jan 2002 02:55:15 +0100 [thread overview]
Message-ID: <200201150155.CAA24369@webserver.ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0201142245040.2118-100000@localhost.localdomain>
> On Mon, 14 Jan 2002, Stephan von Krawczynski wrote:
> >
> > Ok. So what do we do about it? I mean there are possibly some more
people out
> > there with such a problem, or - to my prediction - there will be
more in the
> > future. I see to possibilities:
> > 1) simply increase it overall. I have not the slightest idea what
the drawbacks
> > are. 2) make it configurable (looks like general setup to me).
> >
> > I could provide a patch for either. Do we want that?
>
> I was waiting for hpa to jump on you for suggesting that! but since
> he hasn't yet done so (publicly), here's his mail when I suggested
it
> a month ago (as a temporary aid while tracking down a similar
problem).
>
> That problem was from NTFS overusing vmalloc (and I think Anton has
> now posted the fix), but NTFS wasn't in your list, and I assume you
> didn't have it in statically.
Nope, no ntfs involved here.
I read the former thread. It was in my mind when trying the increased
VMALLOC_RESERVE, and voila, it worked again. I must admit in your case
I was very much thinking that ntfs should be fixed, and I am pleased
the maintainer thought the same :-)
Unfortunately I do not have a good idea about what to do in days where
the graphics cards have more ram onboard than my last workstation had
in total. If I understood Alans' opinion, he thinks basically the
same, what the heck can you do about such monster cards? I don't know,
other than adjusting the RESERVE-area. I have not really thought about
it right now, but I suspect it would be rather impossible to make a
somehow runtime-scalable area working, which would of course be the
complete solution to the underlying problem.
So, what's left? At least configurable? Anybody with a better idea?
Regards,
Stephan
>
next parent reply other threads:[~2002-01-15 1:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0201142245040.2118-100000@localhost.localdomain>
2002-01-15 1:55 ` Stephan von Krawczynski [this message]
2002-01-14 17:12 Memory problem with bttv driver Stephan von Krawczynski
2002-01-14 17:40 ` Alan Cox
2002-01-14 17:43 ` Stephan von Krawczynski
2002-01-14 17:56 ` Alan Cox
2002-01-14 18:38 ` Stephan von Krawczynski
2002-01-14 19:48 ` Stephan von Krawczynski
2002-01-14 20:03 ` Alan Cox
2002-01-14 20:00 ` Stephan von Krawczynski
2002-01-14 21:17 ` Alan Cox
2002-01-14 23:42 ` J.A. Magallon
2002-01-15 10:17 ` Gerd Knorr
2002-01-15 11:14 ` Stephan von Krawczynski
2002-01-15 13:20 ` Gerd Knorr
2002-01-15 13:46 ` Stephan von Krawczynski
2002-01-15 15:16 ` Gerd Knorr
2002-01-15 16:35 ` Stephan von Krawczynski
2002-01-16 9:57 ` Gerd Knorr
2002-01-16 17:24 ` Stephan von Krawczynski
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=200201150155.CAA24369@webserver.ithnet.com \
--to=skraw@ithnet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--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.