public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Andrew Morton <akpm@osdl.org>, Reuben Farrelly <reuben-lkml@reub.net>
Cc: linux-kernel@vger.kernel.org,
	netfilter-devel@lists.netfilter.org, "Seth,
	Rohit" <rohit.seth@intel.com>
Subject: Re: 2.6.14-rc2-mm1 (Oops, possibly Netfilter related?)
Date: Tue, 27 Sep 2005 11:59:16 -0700	[thread overview]
Message-ID: <925820000.1127847556@flay> (raw)
In-Reply-To: <20050927004410.29ab9c03.akpm@osdl.org>

> No, this is simply a warning - the kernel ran out of 1-order pages in the
> page allocator.  There have been several reports of this after
> mm-try-to-allocate-higher-order-pages-in-rmqueue_bulk.patch was merged,
> which was rather expected.
> 
> I've dropped that patch.  Joel Schopp is working on Mel Gorman's patches
> which address fragmentation at this level.  If that code gets there then we
> can take another look at
> mm-try-to-allocate-higher-order-pages-in-rmqueue_bulk.patch.

Me no understand. We're going to deliberately cause fragmentation in order
to defragment it again later ???

M.


  reply	other threads:[~2005-09-27 18:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22  5:28 2.6.14-rc2-mm1 Andrew Morton
2005-09-22  6:35 ` 2.6.14-rc2-mm1 Joel Becker
2005-09-22  6:46 ` 2.6.14-rc2-mm1 Reuben Farrelly
2005-09-22  7:03   ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 18:59 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-22 19:52   ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 20:14     ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-23  0:28       ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-22 22:28     ` 2.6.14-rc2-mm1 - ide problems ? Badari Pulavarty
2005-09-22 23:39       ` Andrew Morton
2005-09-22 19:50 ` tty update speed regression (was: 2.6.14-rc2-mm1) Alexey Dobriyan
2005-09-22 21:49   ` Alexey Dobriyan
2005-09-23  0:08     ` Nishanth Aravamudan
2005-09-23 17:12       ` Nish Aravamudan
2005-09-23 18:42         ` Alexey Dobriyan
2005-09-23 19:07           ` Nishanth Aravamudan
2005-09-23 19:42             ` Alexey Dobriyan
2005-09-23 21:32               ` Nishanth Aravamudan
2005-09-24 17:43 ` 2.6.14-rc2-mm1 Mattia Dongili
2005-09-24 17:58 ` 2.6.14-rc2-mm1 Mattia Dongili
2005-09-24 18:23   ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-26 19:33     ` 2.6.14-rc2-mm1 Seth, Rohit
2005-09-27 18:57       ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 20:05         ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 21:18           ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 21:51             ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 21:59               ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 22:49                 ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 22:49                   ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 23:16                     ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27  7:13 ` 2.6.14-rc2-mm1 (Oops, possibly Netfilter related?) Reuben Farrelly
2005-09-27  7:44   ` Andrew Morton
2005-09-27 18:59     ` Martin J. Bligh [this message]
2005-10-02 17:13       ` Paul Jackson
2005-10-02 21:31         ` Martin J. Bligh
2005-10-03 17:20           ` Rohit Seth
2005-10-03 17:56             ` Martin J. Bligh

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=925820000.1127847556@flay \
    --to=mbligh@mbligh.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=reuben-lkml@reub.net \
    --cc=rohit.seth@intel.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