From: Andrew Shewmaker <agshew@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, Simon Jeons <simon.jeons@gmail.com>,
ric.masonn@gmail.com
Subject: Re: [PATCH v8 3/3] mm: reinititalise user and admin reserves if memory is added or removed
Date: Wed, 10 Apr 2013 09:56:20 -0600 [thread overview]
Message-ID: <CAF-E8XHdkqCUJf28z9GMBNUE84Murdsk=T-CoXoXgkLyrwk2-A@mail.gmail.com> (raw)
In-Reply-To: <20130409151906.2ee55116ca9e3abd80a90e3e@linux-foundation.org>
On Tue, Apr 9, 2013 at 4:19 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 8 Apr 2013 17:00:40 -0400 Andrew Shewmaker <agshew@gmail.com> wrote:
>
>> Should I add the memory notifier code to mm/nommu.c too?
>> I'm guessing that if a system doesn't have an mmu that it also
>> won't be hotplugging memory.
>
> I doubt if we need to worry about memory hotplug on nommu machines,
> so just do the minimum which is required to get nommu to compile
> and link. That's probably "nothing".
I don't know why I didn't think to look for a cross-compiler package first.
Anyway, nommu compiles and links without error when I disable suspend and
switch from slub to slab. Those errors didn't appear to have anything to do
with mm/nommu.c
--
Andrew Shewmaker
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-10 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 19:07 Andrew Shewmaker
2013-04-08 20:37 ` Andrew Morton
2013-04-08 21:00 ` Andrew Shewmaker
2013-04-09 22:19 ` Andrew Morton
2013-04-09 23:56 ` Andrew Shewmaker
2013-04-10 0:05 ` Simon Jeons
2013-04-10 0:11 ` Andrew Shewmaker
2013-04-10 0:14 ` Simon Jeons
2013-04-10 15:56 ` Andrew Shewmaker [this message]
2013-04-09 0:42 ` Andrew Shewmaker
2013-04-08 20:57 ` Andrew Morton
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='CAF-E8XHdkqCUJf28z9GMBNUE84Murdsk=T-CoXoXgkLyrwk2-A@mail.gmail.com' \
--to=agshew@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ric.masonn@gmail.com \
--cc=simon.jeons@gmail.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