mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Keith Mannthey" <kmannth@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Andi Kleen" <ak@suse.de>, "Andrew Morton" <akpm@osdl.org>,
	"Protasevich, Natalie" <Natalie.Protasevich@unisys.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: Double the per cpu area size
Date: Tue, 8 Aug 2006 14:26:15 -0700	[thread overview]
Message-ID: <a762e240608081426k58122a55pc4fe60150c01ed61@mail.gmail.com> (raw)
In-Reply-To: <m1u04n5405.fsf@ebiederm.dsl.xmission.com>

On 8/8/06, Eric W. Biederman <ebiederm@xmission.com> wrote:
> "Keith Mannthey" <kmannth@gmail.com> writes:
>
> > On 8/7/06, Eric W. Biederman <ebiederm@xmission.com> wrote:
> >> Andi Kleen <ak@suse.de> writes:
> >>
> >> >>
> >> >>  #include <asm/pda.h>
> >> >>
> >> >> +#define PERCPU_ENOUGH_ROOM 65536
> >
> > Is it possible to put this into -mm untill things are sorted?
> > 2.6.18-rc3-mm2 x86_64 is still without any per-cpu space for modules.
>
> I think we are sorted (see the later patch to auto size the per cpu
> area).  But you should be ok with current -mm if you compile for 64 or
> fewer cpus.

Yep it looks like the config file I tote around on this box has
CONFIG_NR_CPUS=128. I thought this this was the default NR_CPUS but it
is not.

Thanks,
  Keith

      reply	other threads:[~2006-08-08 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 15:25 Eric W. Biederman
2006-08-07 15:30 ` Andi Kleen
2006-08-07 16:31   ` Eric W. Biederman
2006-08-08 20:43     ` Keith Mannthey
2006-08-08 21:09       ` Eric W. Biederman
2006-08-08 21:26         ` Keith Mannthey [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=a762e240608081426k58122a55pc4fe60150c01ed61@mail.gmail.com \
    --to=kmannth@gmail.com \
    --cc=Natalie.Protasevich@unisys.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®