From: Ralf Baechle <ralf@oss.sgi.com>
To: "Tommy S. Christensen" <tommy.christensen@eicon.com>
Cc: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>,
dony.he@huawei.com, linux-mips@oss.sgi.com
Subject: Re: vmalloc bugs in 2.4.5???
Date: Thu, 27 Dec 2001 19:19:59 -0200 [thread overview]
Message-ID: <20011227191959.B1553@dea.linux-mips.net> (raw)
In-Reply-To: <3C2B45D3.B938CA44@eicon.com>; from tommy.christensen@eicon.com on Thu, Dec 27, 2001 at 05:01:23PM +0100
On Thu, Dec 27, 2001 at 05:01:23PM +0100, Tommy S. Christensen wrote:
> Great! But please make sure that the cache is flushed after the pages
> are allocated instead of before.
>
> With 2.4.9 that still had the cache-flushing in vmalloc_area_pages(), I
> got cache aliasing problems in low memory situations (since alloc_page()
> will re-schedule when no pages are available).
Correct; I fixed that one. That's actually a nasty one, affects all
previous Linux releases. I wonder how this one went unnoticed for so long.
Probably because loading modules is a relativly rare event or so.
Ralf
next prev parent reply other threads:[~2001-12-30 23:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 7:34 vmalloc bugs in 2.4.5??? machael
2001-11-05 7:34 ` machael
2001-11-06 21:08 ` Ralf Baechle
2001-11-07 0:47 ` machael
2001-11-07 0:47 ` machael
2001-11-07 1:39 ` Atsushi Nemoto
2001-11-07 2:09 ` machael
2001-11-07 2:09 ` machael
2001-11-07 10:41 ` Ralf Baechle
2001-11-07 11:29 ` machael
2001-11-07 11:29 ` machael
2001-11-08 15:16 ` Maciej W. Rozycki
2001-12-26 3:32 ` Ralf Baechle
2001-12-27 1:55 ` Atsushi Nemoto
2001-12-27 3:12 ` Ralf Baechle
2001-12-27 3:51 ` Atsushi Nemoto
2001-12-27 4:29 ` Ralf Baechle
2001-12-27 16:01 ` Tommy S. Christensen
2001-12-27 21:19 ` Ralf Baechle [this message]
2001-12-28 0:48 ` machael thailer
2001-12-28 0:48 ` machael thailer
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=20011227191959.B1553@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=dony.he@huawei.com \
--cc=linux-mips@oss.sgi.com \
--cc=nemoto@toshiba-tops.co.jp \
--cc=tommy.christensen@eicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox