linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jungseok Lee <jungseoklee85@gmail.com>
To: linux-mm@kvack.org
Subject: 'atom_size' configuration when a generic setup_per_cpu_ares() is used
Date: Sat, 24 Oct 2015 02:19:13 +0900	[thread overview]
Message-ID: <7E527DCB-C2D1-47D7-A57A-88D37DFEDAD6@gmail.com> (raw)

Greetings,

Nowadays I'm working on 'IRQ Stack' on ARM64 [1]. Like x86, I'd like to
utilize percpu infrastructure for stack allocation, but I've got a challenge.

ARM64 uses a generic setup_per_cpu_areas() described in mm/percpu.c. IOW,
__per_cpu_offset[] is PAGE_SIZE aligned, and it is not possible to allocate
stack with an alignment which is bigger than PAGE_SIZE. At first glance,
the alignment of __per_cpu_offset[] looks controlled by 'atom_size' argument
of pcpu_embed_first_chunk(), but I soon realize that the 'atom_size' is not
configurable in this case.

It would be redundant to introduce ARM64-specific setup_per_cpu_areas() for
a single parameter, atom_size, change. At the same time, it is doubtable to
define an interface, like PERCPU_ENOUGH_ROOM [2], for a single arch support.
I'm not sure which approach is better than the other.

Any comments are greatly welcome.

Thanks in advance!

[1] https://lkml.org/lkml/2015/10/17/75
[2] Since no code uses PERCPU_ENOUGH_ROOM, it could be dropped as clean-up.

--
Best Regards
Jungseok Lee

--
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:[~2015-10-23 17:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7E527DCB-C2D1-47D7-A57A-88D37DFEDAD6@gmail.com \
    --to=jungseoklee85@gmail.com \
    --cc=linux-mm@kvack.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