From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] loop.c oopses
Date: Tue, 16 Jul 2002 02:16:22 -0700 [thread overview]
Message-ID: <20020716091622.GD1096@holomorphy.com> (raw)
In-Reply-To: <3D33E532.E078914E@zip.com.au>
William Lee Irwin III wrote:
>> From watching /proc/meminfo it was clear that there were only 1MB or
>> 2MB under writeback, but it also showed that the dirty memory thresholds
>> were being exceeded.
On Tue, Jul 16, 2002 at 02:19:46AM -0700, Andrew Morton wrote:
> Ah, that may well happen with loop. Mark a page clean, "submit"
> it and that just goes and marks a different page dirty.
> If you could please share the setup details (amount of memory,
> file sizes, workload etc) I'll have a look.
The box is an IBM Thinkpad with 256MB of RAM and a 900MHz P-III cpu.
No-name IDE disk (believe me, I made sure everything there was expendable),
workload being dbench 16 on reiserfs over loop with a 256MB reiserfs loop
file. I'm actually not entirely sure what the filesizes were as dbench
didn't report that.
Cheers,
Bill
next prev parent reply other threads:[~2002-07-16 9:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 6:24 [BUG] loop.c oopses William Lee Irwin III
2002-07-16 7:07 ` Andrew Morton
2002-07-16 8:31 ` Jens Axboe
2002-07-16 8:52 ` Andrew Morton
2002-07-16 8:48 ` Jens Axboe
2002-07-16 9:09 ` Andrew Morton
2002-07-16 8:52 ` William Lee Irwin III
2002-07-16 9:19 ` Andrew Morton
2002-07-16 9:16 ` William Lee Irwin III [this message]
2002-07-16 9:21 ` Jens Axboe
2002-07-16 12:49 ` Rik van Riel
2002-07-16 16:36 ` Jens Axboe
2002-07-16 16:49 ` Rik van Riel
2002-07-16 17:09 ` Jens Axboe
2002-07-16 19:42 ` Jari Ruusu
2002-07-16 21:14 ` William Lee Irwin III
2002-07-16 21:36 ` Andrew Morton
2002-07-17 5:40 ` Jens Axboe
2002-07-17 15:31 ` Jari Ruusu
2002-07-20 17:03 ` William Lee Irwin III
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=20020716091622.GD1096@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=axboe@suse.de \
--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.