From: Daniel Phillips <phillips@bonn-fries.net>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>,
Roger Larsson <roger.larsson@skelleftea.mail.telia.com>,
Stephan von Krawczynski <skraw@ithnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Rik van Riel <riel@conectiva.com.br>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Subject: Re: Memory Problem in 2.4.10-pre2 / __alloc_pages failed
Date: Sun, 2 Sep 2001 22:33:41 +0200 [thread overview]
Message-ID: <20010902202648Z16301-32383+3039@humbolt.nl.linux.org> (raw)
In-Reply-To: <20010902181905Z16091-32383+3020@humbolt.nl.linux.org> <1034195335.999462755@[169.254.198.40]>
In-Reply-To: <1034195335.999462755@[169.254.198.40]>
On September 2, 2001 09:32 pm, Alex Bligh - linux-kernel wrote:
> Daniel,
>
> > What do you do when a new module gets inserted, increasing the high order
> > load and requiring that the slab be expanded? I.e, the need for
> > dependable handling of high order physical allocations doesn't go away
> > entirely. The slab would help even out the situation with atomic allocs
> > because it can be expanded to a target size by a normal task, which can
> > wait.
>
> Yes, chew away to disk as this allocation is non atomic.
What I meant was, the new module implements a network driver which proceeds
to do atomic allocs.
> But this probably still needs something which goes and identifies
> kernel allocated pages with buddies which can be relocated / pushed to
> disk / freed etc.;
>
> Alternatively something to temporarilly hold onto 'nearly freed'
> high-order areas is probably useful. IE if there's an order=3
> allocation stuck waiting for a suitable hole, and there's
> a bit of bitmap that looks like '00010000' (i.e. order 1 hole,
> order 0 hole, order 0 used, order 2 hole), I wonder if we can't
> think of some hueristic to avoid allocating the next order 0
> page request (atomic or not) from the order 0 hole even if
> it's at the front of the order (0) free area list.
One thing I am hearing from some developers is that we don't need to solve
the high-order allocation problems because they are really driver issues -
all drivers should be changed to use scatter-gather or some such. I don't
know if that's correct, this would require knowledge of all driver types and
archs which I can't begin to claim.
I'm quite sure we can fix this up though, not to the point of being able to
guarantee all high order allocations, but to the point where we have a high
probability of success under all loads, as opposed to what we have now which
is very fragile, and not just in the Linus tree.
--
Daniel
next prev parent reply other threads:[~2001-09-02 20:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 18:28 Stephan von Krawczynski
2001-09-02 1:57 ` Daniel Phillips
2001-09-02 2:21 ` Roger Larsson
2001-09-02 4:16 ` Daniel Phillips
2001-09-02 13:48 ` Alex Bligh - linux-kernel
2001-09-02 18:26 ` Daniel Phillips
2001-09-02 19:32 ` Alex Bligh - linux-kernel
2001-09-02 20:24 ` Daniel Phillips
2001-09-02 21:03 ` Alex Bligh - linux-kernel
2001-09-02 20:33 ` Daniel Phillips [this message]
2001-09-02 21:14 ` Alex Bligh - linux-kernel
2001-09-02 21:23 ` Daniel Phillips
2001-09-02 21:28 ` Alex Bligh - linux-kernel
2001-09-02 22:36 ` High order memory allocations (was Re: Memory Problem in 2.4.10-pre2 / __alloc_pages failed) Alex Bligh - linux-kernel
[not found] <689208719.999883299@[10.132.112.53]>
[not found] ` <20010907154801.028a48e8.skraw@ithnet.com>
2001-09-07 21:13 ` Memory Problem in 2.4.10-pre2 / __alloc_pages failed Stephan von Krawczynski
[not found] <Pine.LNX.4.33.0109011021570.280-100000@mikeg.weiden.de>
[not found] ` <20010901055634Z16057-32383+2785@humbolt.nl.linux.org>
2001-09-01 18:54 ` Stephan von Krawczynski
2001-09-02 3:21 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2001-08-29 12:07 Stephan von Krawczynski
2001-08-29 16:47 ` Roger Larsson
2001-08-29 19:18 ` Stephan von Krawczynski
2001-08-30 14:16 ` Stephan von Krawczynski
2001-08-29 23:36 ` Daniel Phillips
2001-08-30 16:49 ` Roger Larsson
2001-08-30 14:46 ` Stephan von Krawczynski
2001-08-30 18:02 ` Daniel Phillips
2001-08-31 10:32 ` Stephan von Krawczynski
2001-08-31 11:06 ` Stephan von Krawczynski
2001-08-31 19:03 ` 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=20010902202648Z16301-32383+3039@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=roger.larsson@skelleftea.mail.telia.com \
--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
all inboxes | Powered by JetHome®