From: Chris Mason <mason@suse.com>
To: marc heckmann <heckmann@hbesoftware.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: 2.4.8-pre7: still buffer cache problems
Date: Thu, 09 Aug 2001 12:09:11 -0400 [thread overview]
Message-ID: <382140000.997373351@tiny> (raw)
In-Reply-To: <32774.213.7.60.90.997365391.squirrel@webmail.hbesoftware.com>
On Thursday, August 09, 2001 09:56:31 AM -0400 marc heckmann
<heckmann@hbesoftware.com> wrote:
> Hi.
>
> While 2.4.8-pre7 definitely fixes the "dd if=/dev/zero of=bigfile bs=1000k
> count=bignumber" case. The "dd if=/dev/hda of=/dev/null" is still quite
> broken for me. while I appreciate that it is a case of "root" doing
> something stupid, it shouldn't mess up the system so badly. On 2.2.19 the
> system is completely useable. on 2.4.8-pre7 it's thrashing swap like mad
> and the buffercache is huge. this is all on a PPC [G3] w/ 192Mb's of RAM
> and 200MB's of swap. so no highmem is involved. vmstat outputs:
>
Hmmm, perhaps its because the buffer cache doesn't have any use-once or
drop behind optimizations?
What happens when you do this instead (assuming your dd supports large
files, otherwise use 1000 instead of 9000)
dd if=/dev/zero of=some_file seek=9000 bs=1MB count=1
Then, run your test again:
dd if=some_file of=/dev/null
-chris
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-08-09 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 13:56 marc heckmann
2001-08-09 16:09 ` Chris Mason [this message]
2001-08-09 20:55 ` Rik van Riel
2001-08-10 0:20 ` marc heckmann
2001-08-15 11:06 ` 2.4.8-pre7: still buffer cache problems[+2.4.9-pre3 comments] Marc Heckmann
2001-08-10 1:52 ` 2.4.8-pre7: still buffer cache problems Ed Tomlinson
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=382140000.997373351@tiny \
--to=mason@suse.com \
--cc=heckmann@hbesoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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