From: Miquel van Smoorenburg <miquels@cistron.nl>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.46: kernel BUG at kernel/timer.c:333!
Date: Mon, 11 Nov 2002 11:57:56 +0100 [thread overview]
Message-ID: <20021111115756.A12243@cistron.nl> (raw)
In-Reply-To: <3DCE93CF.79AF516C@digeo.com>; from akpm@digeo.com on Sun, Nov 10, 2002 at 09:13:51AM -0800
According to Andrew Morton:
> Miquel van Smoorenburg wrote:
> >
> > I've booted 2.5.46bk5 on the machine, and it has been running for over
> > 2 hours with extra heavy diskio. That reliably crashed the machine
> > in about 45 minutes with 2.4.45 and 2.5.46, machine is still up now.
>
> OK, thanks.
It survived the night and is still up. Looks like it runs slightly
faster than 2.4.20-X.
> This is a blockdev which was under mmap(), yes? No, I haven't looked at
> that yet. It'll be a matter of just killing the warning.
OK.
> mmapping a blockdev is a pretty dopey thing to do, btw. It doesn't
> allow the use of highmem, the IO uses tiny BIOs (in fact I think
> it uses 512-byte or 1k blocksize too) and there are buffer_heads
> all over the place. You'll get better results from mmapping a
> regular file.
It's just that the news server uses its own 'filesystem'. It does
normal read/write i/o on it, but the allocation bitmap at the
beginning of the 'file' is mmap()ed. Using a regular file means
creating a 160 GB file, the triple indirect blocks will probably
kill performance.
I guess that means I have to resurrect rawfs, then (a filesystem
I wrote for 2.2 that shows partitions as fixed-size files). But
that seems so .. unnecessary.
Mike.
next prev parent reply other threads:[~2002-11-11 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 15:07 2.5.46: kernel BUG at kernel/timer.c:333! Miquel van Smoorenburg
2002-11-09 18:51 ` Andrew Morton
2002-11-10 14:32 ` Miquel van Smoorenburg
2002-11-10 17:13 ` Andrew Morton
2002-11-11 10:57 ` Miquel van Smoorenburg [this message]
2002-11-11 18:13 ` Andrew Morton
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=20021111115756.A12243@cistron.nl \
--to=miquels@cistron.nl \
--cc=akpm@digeo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox