linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Christoph Lameter <cl@linux.com>, Nick Piggin <npiggin@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"randy.dunlap_ocs10g@oracle.com" <randy.dunlap_ocs10g@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Paul Mundt <lethal@linux-sh.org>,
	"iwamatsu.nobuhiro@renesas.com" <iwamatsu.nobuhiro@renesas.com>
Subject: Re: linux-next ia64 build problems in slqb
Date: Tue, 21 Apr 2009 22:07:16 +0300	[thread overview]
Message-ID: <84144f020904211207q736bfc44n4cd622536cd0a67@mail.gmail.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA39EC57748@orsmsx505.amr.corp.intel.com>

Hi Tony,

On Tue, Apr 21, 2009 at 9:45 PM, Luck, Tony <tony.luck@intel.com> wrote:
>> Interesting. What exactly is an UP NUMA machine?
>
> UP + NUMA is a special case of memory-only nodes.  There are
> some (crazy?) customers with problems that require very large
> amounts of memory, but not very much cpu horse power.  They
> buy large multi-node systems and populate all the nodes with
> as much memory as they can afford, but most nodes get zero
> cpus.

Oh, cool. Thanks for the explanation!

On Tue, Apr 21, 2009 at 9:45 PM, Luck, Tony <tony.luck@intel.com> wrote:
>> Anyway, I'm more than
>> happy to apply a tested patch to fix up SLQB. Nick?
>
> I'm trying to check whether http://lkml.org/lkml/2009/4/20/30
> fixes things.  It certainly solves the complilation problem,
> but I'm running into apparently unrelated issues trying to
> boot linux-next kernels.

Great! You can try it on top of the "topic/slqb/core" branch of

  git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6.git

if you want. It's basically plain 2.6.30-rc1 plus SLQB.

One minor nit: the patch should define an empty static inline of
claim_remote_free_list() for the !SMP case. I can fix it at my end
before merging, though, if necessary.

                                       Pekka

  reply	other threads:[~2009-04-21 19:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 22:08 linux-next ia64 build problems in slqb Luck, Tony
2009-04-20 23:42 ` Randy Dunlap
2009-04-20 23:59   ` Luck, Tony
2009-04-21  5:51 ` Pekka Enberg
2009-04-21  6:29   ` Paul Mundt
2009-04-21 14:35   ` Christoph Lameter
2009-04-21 18:25     ` Pekka Enberg
2009-04-21 18:45       ` Luck, Tony
2009-04-21 19:07         ` Pekka Enberg [this message]
2009-04-21 22:31           ` Luck, Tony
2009-04-22  7:02             ` Pekka J Enberg
2009-04-23  5:50               ` Paul Mundt

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=84144f020904211207q736bfc44n4cd622536cd0a67@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=iwamatsu.nobuhiro@renesas.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=randy.dunlap_ocs10g@oracle.com \
    --cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).