From: Robert Love <rml@tech9.net>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Arjan Filius <iafilius@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: Feedback on preemptible kernel patch
Date: 10 Sep 2001 01:09:52 -0400 [thread overview]
Message-ID: <1000098594.18895.1.camel@phantasy> (raw)
In-Reply-To: <20010910031728Z16177-26183+705@humbolt.nl.linux.org>
In-Reply-To: <Pine.LNX.4.33.0109092317330.16723-100000@sjoerd.sjoerdnet> <1000071474.16805.20.camel@phantasy> <20010910031728Z16177-26183+705@humbolt.nl.linux.org>
On Sun, 2001-09-09 at 23:24, Daniel Phillips wrote:
> This may not be your fault. It's a GFP_NOFS recursive allocation - this
> comes either from grow_buffers or ReiserFS, probably the former. In
> either case, it means we ran completely out of free pages, even though
> the caller is willing to wait. Hmm. It smells like a loophole in vm
> scanning.
I am not a VM hacker -- can you tell me where to start? what do you
suspect it is?
If the user stops seeing the error with preemption disabled, is your
theory nulled, or does that just mean the problem is agitated by
preemption?
I don't think Arjan was using ReiserFS, so its from grow_buffers...
I appreciate your help.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-10 5:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 5:22 Feedback on preemptible kernel patch grue
2001-09-08 5:47 ` Robert Love
2001-09-08 17:33 ` Arjan Filius
2001-09-08 18:22 ` safemode
2001-09-08 20:58 ` [SMP lock BUG?] " Roger Larsson
2001-09-08 22:18 ` Arjan Filius
2001-09-09 14:55 ` george anzinger
2001-09-09 22:25 ` Arjan Filius
2001-09-09 4:40 ` Robert Love
2001-09-09 17:09 ` Robert Love
2001-09-09 21:07 ` Arjan Filius
2001-09-09 21:26 ` Robert Love
2001-09-09 21:23 ` Arjan Filius
2001-09-09 21:37 ` Robert Love
2001-09-10 3:24 ` Daniel Phillips
2001-09-10 3:37 ` Jeremy Zawodny
2001-09-10 5:09 ` Robert Love [this message]
2001-09-10 18:25 ` Daniel Phillips
2001-09-10 21:29 ` Arjan Filius
2001-09-13 17:27 ` Robert Love
2001-09-14 7:30 ` george anzinger
2001-09-14 15:01 ` Robert Love
2001-09-11 19:47 ` Arjan Filius
2001-09-09 18:57 ` grue
2001-09-09 21:44 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-11 22:53 Robert Love
2001-09-14 2:47 Dieter Nützel
[not found] <200109140302.f8E32LG13400@zero.tech9.net>
2001-09-14 4:35 ` Robert Love
2001-09-15 4:25 ` Dieter Nützel
[not found] ` <200109150444.f8F4iEG19063@zero.tech9.net>
2001-09-15 5:14 ` Robert Love
2001-09-18 4:06 ` Dieter Nützel
2001-09-18 8:35 ` Daniel Phillips
2001-09-18 18:18 ` Roger Larsson
2001-09-18 23:31 ` Robert Love
2001-09-20 6:40 ` Dieter Nützel
[not found] ` <200109180406.f8I46LG02238@zero.tech9.net>
2001-09-18 23:31 ` Robert Love
[not found] <Pine.LNX.4.33.0109140838040.21992-100000@sjoerd.sjoerdnet>
2001-09-14 15:04 ` Robert Love
2001-09-15 9:44 ` Arjan Filius
2001-09-15 10:38 ` Erik Mouw
2001-09-15 17:57 ` Robert Love
2001-09-15 19:18 Robert Love
2001-09-16 1:28 ` Daniel Phillips
2001-09-16 1:54 ` Daniel Phillips
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=1000098594.18895.1.camel@phantasy \
--to=rml@tech9.net \
--cc=iafilius@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox