From: "J.A. Magallon" <jamagallon@able.es>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>
Cc: Austin Gonyou <austin@digitalroadkill.net>, linux-kernel@vger.kernel.org
Subject: Re: Terrible VM in 2.4.11+?
Date: Tue, 9 Jul 2002 00:58:16 +0200 [thread overview]
Message-ID: <20020708225816.GA1948@werewolf.able.es> (raw)
In-Reply-To: <20020709005025.B1745@mail.muni.cz>; from xhejtman@mail.muni.cz on Tue, Jul 09, 2002 at 00:50:25 +0200
On 2002.07.09 Lukas Hejtmanek wrote:
>
>Yes, I know a few people that reports it works well for them. How ever for me
>and some other do not. System is redhat 7.2, ASUS A7V MB, /dev/hda is on promise
>controller. Following helps a lot:
>
>while true; do sync; sleep 3; done
>
>How did you modify the params of bdflush? I do not want to suspend i/o buffers
>nor disk cache..
>
>Another thing to notice, the X server has almost every time some pages swaped to
>the swap space on /dev/hda. When bdflushd is flushing buffers X server stops as
>has no access to the swap area during i/o lock.
>
>On Mon, Jul 08, 2002 at 05:37:02PM -0500, Austin Gonyou wrote:
>> I do things like this regularly, and have been using kernels 2.4.10+ on
>> many types of boxen, but have yet to see this behavior. I've done this
>> same type of test with 16k blocks up to 10M, and not had this problem I
>> usually do test with regard to I/O on SCSI, but have tested on IDE,
>> since we use many IDE systems for developers. I found though, that using
>> something like LVM, and overwhelming it, causes bdflush to go crazy. I
>> can hit the wall you refer to then.When bdflushd is too busy...it does
>> in fact seem to *lock* the system, but of course..it's just bdflush
>> doing it's thing. If I modify the bdflush params..this causes things to
>> work just fine, at least, useable.
>
Seriously, if you have that kind of problems, take the -aa kernel and use it.
I use it regularly and it behaves as one would expect, and fast.
And please, report your results...
--
J.A. Magallon \ Software is like sex: It's better when it's free
mailto:jamagallon@able.es \ -- Linus Torvalds, FSF T-shirt
Linux werewolf 2.4.19-rc1-jam1, Mandrake Linux 8.3 (Cooker) for i586
gcc (GCC) 3.1.1 (Mandrake Linux 8.3 3.1.1-0.7mdk)
next prev parent reply other threads:[~2002-07-08 22:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 22:11 Lukas Hejtmanek
2002-07-08 22:37 ` Austin Gonyou
2002-07-08 22:50 ` Lukas Hejtmanek
2002-07-08 22:58 ` J.A. Magallon [this message]
2002-07-08 23:58 ` Lukas Hejtmanek
2002-07-09 10:48 ` Terrible VM in 2.4.11+ again? Lukas Hejtmanek
2002-07-10 16:34 ` Andrea Arcangeli
[not found] ` <20020801113124.GA755@mail.muni.cz>
[not found] ` <20020801140348.GM1132@dualathlon.random>
[not found] ` <20020801141940.GB755@mail.muni.cz>
2002-08-01 15:39 ` Terrible VM in 2.4.19rc3aa4 once again? Andrea Arcangeli
[not found] ` <20020801220143.GC755@mail.muni.cz>
2002-08-01 22:14 ` Andrea Arcangeli
2002-07-10 8:43 ` Terrible VM in 2.4.11+? Thomas Tonino
2002-07-10 8:49 ` Jens Axboe
2002-07-10 13:52 ` Thomas Tonino
2002-07-10 16:41 ` Andrea Arcangeli
2002-07-10 12:34 ` Adrian Bunk
2002-07-08 23:04 ` Austin Gonyou
2002-07-08 23:27 ` khromy
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=20020708225816.GA1948@werewolf.able.es \
--to=jamagallon@able.es \
--cc=austin@digitalroadkill.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@mail.muni.cz \
/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
all inboxes | Powered by JetHome®