From: Stephan von Krawczynski <skraw@ithnet.com>
To: Roger Larsson <roger.larsson@norran.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Upd: [PATCH NG] alloc_pages_limit & pages_min
Date: Fri, 24 Aug 2001 11:25:20 +0200 [thread overview]
Message-ID: <20010824112520.5f01626f.skraw@ithnet.com> (raw)
In-Reply-To: <200108231933.f7NJX8j21551@mailc.telia.com>
In-Reply-To: <Pine.LNX.4.33L.0108231600020.31410-100000@duckman.distro.conectiva> <200108231933.f7NJX8j21551@mailc.telia.com>
On Thu, 23 Aug 2001 21:28:44 +0200
Roger Larsson <roger.larsson@norran.net> wrote:
> Riel convinced be to back off a part of the patch.
> Here comes an updated one.
Hello Roger,
this does not solve my problem with NFS-copies. Just for information. I tried and did not work.
Besides I expected the patch to make the free pages pool somehow bigger during file-copies, but ended up with this situation:
total: used: free: shared: buffers: cached:
Mem: 921726976 918573056 3153920 0 12337152 816504832
Swap: 271392768 0 271392768
MemTotal: 900124 kB
MemFree: 3080 kB
MemShared: 0 kB
Buffers: 12048 kB
Cached: 797368 kB
SwapCached: 0 kB
Active: 473628 kB
Inact_dirty: 331796 kB
Inact_clean: 3992 kB
Inact_target: 1940 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 900124 kB
LowFree: 3080 kB
SwapTotal: 265032 kB
SwapFree: 265032 kB
The MemFree isn't really a lot compared to inact_dirty. knfsd fails at least.
Regards, Stephan
next prev parent reply other threads:[~2001-08-24 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 23:46 [PATCH NG] alloc_pages_limit & pages_min Roger Larsson
2001-08-23 0:40 ` Rik van Riel
2001-08-23 18:36 ` Roger Larsson
2001-08-23 18:44 ` Rik van Riel
2001-08-23 18:52 ` Roger Larsson
2001-08-23 19:03 ` Rik van Riel
2001-08-23 19:28 ` Upd: " Roger Larsson
2001-08-23 19:28 ` Roger Larsson
2001-08-24 9:25 ` Stephan von Krawczynski [this message]
2001-08-24 10:28 ` Roger Larsson
2001-08-24 12:50 ` Stephan von Krawczynski
2001-08-23 18:45 ` Roger Larsson
2001-08-23 18:55 ` Rik van Riel
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=20010824112520.5f01626f.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@norran.net \
/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.