From: Stephan von Krawczynski <skraw@ithnet.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vm rewrite ready [Re: broken VM in 2.4.10-pre9]
Date: Tue, 18 Sep 2001 11:00:48 +0200 [thread overview]
Message-ID: <20010918110048.095af437.skraw@ithnet.com> (raw)
In-Reply-To: <20010918004116.A698@athlon.random>
In-Reply-To: <Pine.LNX.4.33L2.0109160031500.7740-100000@flashdance> <9o1dev$23l$1@penguin.transmeta.com> <1000722338.14005.0.camel@x153.internalnet> <20010916203414.B1315@athlon.random> <20010917174037.7e3739b9.skraw@ithnet.com> <20010918004116.A698@athlon.random>
On Tue, 18 Sep 2001 00:41:16 +0200 Andrea Arcangeli <andrea@suse.de> wrote:
> [ CC'ed to l-k with Stephan approval ]
> > - cpu average load is low, during whole test sometimes even below 3
> > (never saw
> > this before)
>
> Good.
>
> I also had another report with very vfs intensive operation going on and
> I suspect this patch will be a good idea (even if it can lead to the
> usual excessive grow of the vfs caches on the long run but the current
> way is probably too aggressive).
Hm, are you sure about this? Here is /proc/meminfo after a night of heavy nfs
action (we are at the server side):
total: used: free: shared: buffers: cached:
Mem: 923574272 919187456 4386816 0 39723008 793706496
Swap: 271392768 1417216 269975552
MemTotal: 901928 kB
MemFree: 4284 kB
MemShared: 0 kB
Buffers: 38792 kB
Cached: 775052 kB
SwapCached: 52 kB
Active: 811464 kB
Inactive: 2432 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 901928 kB
LowFree: 4284 kB
SwapTotal: 265032 kB
SwapFree: 263648 kB
You see most mem found its way in the active queue. If you talk about
"aggressive" meaning aggressively aged or even freed, I cannot see it.
I will go on for another day without additional patching and see how things
evolve and how the system behaves in interactive situation.
Ah, another thing to mention. I got some _new_ alloc failures:
Sep 18 04:16:49 admin kernel: nfsd __alloc_pages: 1-order allocation failed
(gfp=0x20/0) from c012de72
Sep 18 04:17:27 admin kernel: nfsd __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c012de72
Sep 18 04:21:18 admin kernel: gzip __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c012de72
c012de5c T _alloc_pages
c012de74 t balance_classzone
Hope this helps,
Stephan
next prev parent reply other threads:[~2001-09-18 9:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 22:43 broken VM in 2.4.10-pre9 Peter Magnusson
2001-09-15 23:50 ` Jan Harkes
2001-09-16 5:31 ` Linus Torvalds
2001-09-16 8:45 ` Eric W. Biederman
2001-09-17 10:25 ` Tonu Samuel
2001-09-16 16:47 ` Jeremy Zawodny
2001-09-16 18:36 ` Alan Cox
2001-09-16 19:38 ` Linus Torvalds
2001-09-16 18:34 ` vm rewrite ready [Re: broken VM in 2.4.10-pre9] Andrea Arcangeli
2001-09-16 19:07 ` Rik van Riel
2001-09-16 15:19 ` broken VM in 2.4.10-pre9 Phillip Susi
2001-09-16 19:33 ` Jeremy Zawodny
2001-09-16 19:54 ` [PATCH] " Rik van Riel
2001-09-16 19:52 ` Rik van Riel
2001-09-16 19:17 ` vm rewrite ready [Re: broken VM in 2.4.10-pre9] Alan Cox
2001-09-16 19:15 ` Rik van Riel
2001-09-16 19:19 ` Andrea Arcangeli
2001-09-16 19:30 ` Linus Torvalds
[not found] ` <20010917174037.7e3739b9.skraw@ithnet.com>
[not found] ` <20010917181040.J713@athlon.random>
[not found] ` <20010917191256.6e6a1c87.skraw@ithnet.com>
2001-09-17 22:41 ` Andrea Arcangeli
2001-09-18 9:00 ` Stephan von Krawczynski [this message]
2001-09-16 19:37 ` broken VM in 2.4.10-pre9 Linus Torvalds
2001-09-17 14:04 ` Olaf Zaplinski
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=20010918110048.095af437.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=andrea@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.