From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: kernel-janitors@vger.kernel.org
Subject: Re: [tip:master 30/35] mm/memory.c:72:2: warning: #warning Unfortunate NUMA config, growing page-fra
Date: Fri, 28 Sep 2012 10:25:24 +0000 [thread overview]
Message-ID: <1348827924.3292.70.camel@twins> (raw)
In-Reply-To: <20120928095526.GA28747@localhost>
On Fri, 2012-09-28 at 17:55 +0800, Fengguang Wu wrote:
> Hi Peter,
>
> FYI, there are new compile warnings show up in
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> head: 2ef756a2e79149dc84c88f7ccc42ec38cbb7722e
> commit: 835e3cf29f4eeba6c5c8bcc188b2138029157938 [30/35] mm: Fold page::nid_last into page::flags when possible
> config: i386-allmodconfig
>
> All warnings:
>
> mm/memory.c:72:2: warning: #warning Unfortunate NUMA config, growing page-frame for last_nid. [-Wcpp]
Yeah, 32bit NUMA config.. nobody sane should be doing or using that.
The other option was to hard-disable 32bit support for SCHED_NUMA, which
I wouldn't mind either.. who gives about 32 bits computing anyway ;-)
prev parent reply other threads:[~2012-09-28 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 9:55 [tip:master 30/35] mm/memory.c:72:2: warning: #warning Unfortunate NUMA config, growing page-frame f Fengguang Wu
2012-09-28 10:25 ` Peter Zijlstra [this message]
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=1348827924.3292.70.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=kernel-janitors@vger.kernel.org \
/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