From: Stephan von Krawczynski <skraw@ithnet.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: marcelo.tosatti@cyclades.com.br, neilb@cse.unsw.edu.au,
linux-kernel@vger.kernel.org
Subject: Re: experiences beyond 4 GB RAM with 2.4.22
Date: Tue, 16 Sep 2003 14:05:57 +0200 [thread overview]
Message-ID: <20030916140557.663b26b4.skraw@ithnet.com> (raw)
In-Reply-To: <20030916102113.0f00d7e9.skraw@ithnet.com>
On Tue, 16 Sep 2003 10:21:13 +0200
Stephan von Krawczynski <skraw@ithnet.com> wrote:
> On Mon, 15 Sep 2003 19:01:42 -0300 (BRT)
> Marcelo Tosatti <marcelo.tosatti@cyclades.com.br> wrote:
>
> > > I already thought about that and tried. In fact it is as fast and fine as
> > > 2 GB setup. It runs really smooth.
> > > The really simple test for the problem is running "updatedb" (find over
> > > the whole filesystem). The box comes to a crawl while this is running,
> > > network is absolutely bad, interactivity is rather dead, very often not
> > > even a ssh login works.
> >
> > Does -pre4 (with the VM changes from Andrea) show any difference? There
> > are significant changes in the per-zone decisions which might help.
>
> Hello Marcelo,
>
> it looks like -pre4 performs not well even in 4 GB environment. After few
> days of running I find hanging 2.4.22 nfs-clients on a 2.4.23-pre4 server.
>
> On the client I get a bunch of those:
>
> Sep 16 03:02:00 brenda kernel: nfs: server 192.168.1.1 OK
> [...]
Hello again,
you will love to hear that you can drop the above statement completely. After
digging deeper into the case I found out that it was caused by a dead switch.
So this is no -pre4 problem, but a hardware issue. The switch corrupted about
every 20th packet.
So I can tell nothing negative so far about -pre4 with 4 GB.
I'll try with 6 GB now.
Regards,
Stephan
next prev parent reply other threads:[~2003-09-16 12:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 9:01 experiences beyond 4 GB RAM with 2.4.22 Stephan von Krawczynski
2003-09-09 12:25 ` Andrea Arcangeli
2003-09-12 2:46 ` Neil Brown
2003-09-12 6:54 ` Stephan von Krawczynski
2003-09-12 7:11 ` Jens Axboe
2003-09-12 7:53 ` Mike Fedyk
2003-09-15 22:01 ` Marcelo Tosatti
2003-09-16 8:21 ` Stephan von Krawczynski
2003-09-16 12:05 ` Stephan von Krawczynski [this message]
2003-09-16 13:11 ` Marcelo Tosatti
2003-09-16 13:36 ` Stephan von Krawczynski
2003-09-16 13:55 ` Richard B. Johnson
2003-09-16 14:13 ` Stephan von Krawczynski
2003-09-16 14:33 ` Marcelo Tosatti
2003-09-16 14:36 ` Stephan von Krawczynski
2003-09-16 14:36 ` Alan Cox
2003-09-16 15:20 ` Stephan von Krawczynski
2003-09-16 15:29 ` Alan Cox
2003-09-16 15:49 ` Timothy Miller
2003-09-16 16:17 ` Stephan von Krawczynski
2003-09-16 19:58 ` Olivier Galibert
2003-09-17 15:10 ` Alan Cox
2003-09-17 19:19 ` Jens Axboe
2003-09-17 19:30 ` Marcelo Tosatti
2003-09-17 22:18 ` Stephan von Krawczynski
2003-09-18 7:08 ` Jens Axboe
2003-09-18 7:12 ` Jens Axboe
2003-09-18 11:22 ` Stephan von Krawczynski
2003-09-18 15:05 ` William Lee Irwin III
2003-09-16 17:10 ` Pavel Machek
2003-09-16 19:53 ` Olivier Galibert
2003-09-16 20:04 ` Pavel Machek
2003-09-16 21:16 ` Marcelo Tosatti
2003-09-16 21:23 ` Olivier Galibert
2003-09-17 11:14 ` Stephan von Krawczynski
2003-09-17 13:08 ` Olivier Galibert
2003-09-18 9:58 ` Olivier Galibert
2003-09-18 10:13 ` Stephan von Krawczynski
2003-09-18 11:22 ` Olivier Galibert
2003-09-17 6:41 ` Rogier Wolff
2003-09-17 10:26 ` Jens Axboe
2003-09-17 10:42 ` Rogier Wolff
2003-09-17 10:53 ` Jens Axboe
2003-09-17 19:19 ` Pavel Machek
2003-09-18 11:39 ` Rogier Wolff
2003-09-18 12:13 ` Rogier Wolff
2003-09-16 15:22 ` Timothy Miller
2003-09-16 15:29 ` Martin J. Bligh
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=20030916140557.663b26b4.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=neilb@cse.unsw.edu.au \
/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