linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Michal Hocko <mhocko@kernel.org>, Jiri Kosina <jkosina@suse.cz>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: pcpu allocator on large NUMA machines
Date: Tue, 25 Jul 2017 12:39:57 -0400	[thread overview]
Message-ID: <20170725163957.GA3216015@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <877eyxz4r8.fsf@concordia.ellerman.id.au>

Hello, Michael.

On Tue, Jul 25, 2017 at 11:26:03AM +1000, Michael Ellerman wrote:
> I don't think we want to stop using embed first chunk unless we have to.
> 
> We have code that accesses percpu variables in real mode (with the MMU
> off), and that wouldn't work easily if the first chunk wasn't in the
> linear mapping. So it's not just an optimisation for us.
> 
> We can fairly easily make the vmalloc space 56T, and I'm working on a
> patch to make it ~500T on newer machines.

Yeah, the only constraint is the size of vmalloc area in relation to
the maximum spread across NUMA regions.  If the vmalloc space can be
made bigger, that'd be the best option.  As the area percpu allocator
actually uses is very small comparatively, it doesn't have to be a lot
larger either.

Thanks.

-- 
tejun

--
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>

      reply	other threads:[~2017-07-25 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 13:42 Michal Hocko
2017-07-24 13:57 ` Tejun Heo
2017-07-24 14:28   ` Michal Hocko
2017-07-25  1:26     ` Michael Ellerman
2017-07-25 16:39       ` Tejun Heo [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=20170725163957.GA3216015@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mpe@ellerman.id.au \
    /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