From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Upd: [PATCH NG] alloc_pages_limit & pages_min
Date: Fri, 24 Aug 2001 12:28:13 +0200 [thread overview]
Message-ID: <200108241034.f7OAYPA07047@mailf.telia.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108231600020.31410-100000@duckman.distro.conectiva> <200108231933.f7NJX8j21551@mailc.telia.com> <20010824112520.5f01626f.skraw@ithnet.com>
In-Reply-To: <20010824112520.5f01626f.skraw@ithnet.com>
On Fridayen den 24 August 2001 11:25, Stephan von Krawczynski wrote:
> 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:
>
> [snip]
>
> The MemFree isn't really a lot compared to inact_dirty. knfsd fails at
> least.
Wait a minute - knfsd... hmm...
Suppose knfsd allock without the wait flag - then it could cause this problems
by itself...
> Aug 21 20:14:51 admin kernel: __alloc_pages: 3-order allocation failed
> (gfp=0x20/0).
Who is doing thise allocs?
Add a printout of current->pid with format %d
I bet it is knfsd itself (or a driver it uses).
Another thing to try is to run with non kernel nfs...
/RogerL
--
Roger Larsson
Skellefteå
Sweden
next prev parent reply other threads:[~2001-08-24 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L.0108231600020.31410-100000@duckman.distro.conectiva>
2001-08-23 19:28 ` Upd: [PATCH NG] alloc_pages_limit & pages_min Roger Larsson
2001-08-24 9:25 ` Stephan von Krawczynski
2001-08-24 10:28 ` Roger Larsson [this message]
2001-08-24 12:50 ` Stephan von Krawczynski
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=200108241034.f7OAYPA07047@mailf.telia.com \
--to=roger.larsson@skelleftea.mail.telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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