From: Paul Mundt <lethal@linux-sh.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Bryan Wu <bryan.wu@analog.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
uclinux-dist-devel@blackfin.uclinux.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] Blackfin arch: add some missing syscall
Date: Thu, 13 Sep 2007 17:47:03 +0900 [thread overview]
Message-ID: <20070913084703.GA28094@linux-sh.org> (raw)
In-Reply-To: <20070913081852.GC17367@parisc-linux.org>
On Thu, Sep 13, 2007 at 02:18:52AM -0600, Matthew Wilcox wrote:
> On Thu, Sep 13, 2007 at 03:56:43PM +0800, Bryan Wu wrote:
> > +/* Not relevant on no-mmu */
>
> I thought this list seemed a little long, so I investigated a couple
> of them. mbind makes sense (it's only implemented for NUMA ... a NUMA
> embedded platform? not the kind which runs applications that use mbind),
There are embedded platforms that are using NUMA memory policies,
including mbind() in applications for setting them. Page migration is a
little iffier, but that can be turned off. Embedded platforms with
multiple memories (and a different cost per memory) are quite common, and
they're getting large enough to offset the overhead of a pgdat + bootmem
map. We have them on nommu also, but that's not been hacked up generically yet.
prev parent reply other threads:[~2007-09-13 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 7:56 [PATCH] Blackfin arch: add some missing syscall Bryan Wu
2007-09-13 8:07 ` Paul Mundt
2007-09-13 8:09 ` Paul Mundt
2007-09-13 8:18 ` Matthew Wilcox
2007-09-13 8:37 ` Mike Frysinger
2007-09-13 8:57 ` Bryan Wu
2007-09-13 11:03 ` [Uclinux-dist-devel] " Bernd Schmidt
2007-09-14 5:45 ` Bryan Wu
2007-09-14 6:44 ` Mike Frysinger
2007-09-14 7:32 ` Bryan Wu
2007-09-15 1:28 ` Mike Frysinger
2007-09-13 8:47 ` Paul Mundt [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=20070913084703.GA28094@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=uclinux-dist-devel@blackfin.uclinux.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;
as well as URLs for NNTP newsgroup(s).