public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: experiences beyond 4 GB RAM with 2.4.22
Date: Fri, 12 Sep 2003 08:54:35 +0200	[thread overview]
Message-ID: <20030912085435.6a26fec4.skraw@ithnet.com> (raw)
In-Reply-To: <16225.13206.910616.386713@notabene.cse.unsw.edu.au>

On Fri, 12 Sep 2003 12:46:46 +1000
Neil Brown <neilb@cse.unsw.edu.au> wrote:

> > Both are 2.4.22. 192.168.1.1 is the testbox. I saw those with 2GB, but
> > could fix it through more nfs-daemons and
> > 
> >         echo 2097152 >/proc/sys/net/core/rmem_max
> >         echo 2097152 >/proc/sys/net/core/wmem_max
> > 
> > Are these values too small for 6 GB?
> 
> No.  The values are proportional to the number of server threads, not
> the amount of RAM... and they should be un-necessary after 2.4.20
> anyway as nfsd in the kernel makes the appropriate settings.

Oh. That's interesting. Then everything should be the same if I deleted
those...

> > 2) Box is very slow, kswapd looks very active during tar of a local
> > harddisk. Interactivity is really bad. Seems vm has a high time looking for
> > free or usable pages. Compared to 2 GB the behaviour is unbelievably bad.
> > 
> > 3) Network performance has a remarkable dropdown during above tar. In fact
> > doing simple pings every few minutes shows that quite a lot of them are
> > simply dropped, never make it over the ethernet.
> 
> My only guess is that it is doing a lot of copying into low memory
> because your devices can only DMA into/outof low memory.

I forgot to mention: Both network card and controller are 64 bit cards.
Network card is (vendor 3com):
Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet
(rev 15) (tg3-driver)
Controller is:
RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 01)
I have "CONFIG_HIGHIO=y"

> Have you tried 2.6 ??

No, not yet. I have not dared :-)

> How about CONFIG_HIGHMEM4G ?
> It won't use all the RAM, but it would be interesting if it were
> faster.

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.

Regards,
Stephan

  reply	other threads:[~2003-09-12  6:54 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 [this message]
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
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=20030912085435.6a26fec4.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --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