Re: [PATCH 00/05] robust per_cpu allocation for modules
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Subject: Re: [PATCH 00/05] robust per_cpu allocation for modules
- From: Paul Mackerras <paulus@xxxxxxxxx>
- Date: Sun, 16 Apr 2006 17:02:19 +1000
- Cc: Nick Piggin <nickpiggin@xxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Andi Kleen <ak@xxxxxxx>, Martin Mares <mj@xxxxxxxxxxxxxxxxxxxxxxxx>, bjornw@xxxxxxxx, schwidefsky@xxxxxxxxxx, benedict.gaster@xxxxxxxxxx, lethal@xxxxxxxxxxxx, Chris Zankel <chris@xxxxxxxxxx>, Marc Gauthier <marc@xxxxxxxxxxxxx>, Joe Taylor <joe@xxxxxxxxxxxxx>, David Mosberger-Tang <davidm@xxxxxxxxxx>, rth@xxxxxxxxxxx, spyro@xxxxxxx, starvik@xxxxxxxx, tony.luck@xxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, ralf@xxxxxxxxxxxxxx, linux-mips@xxxxxxxxxxxxxx, grundler@xxxxxxxxxxxxxxxx, parisc-linux@xxxxxxxxxxxxxxxx, linuxppc-dev@xxxxxxxxxx, linux390@xxxxxxxxxx, davem@xxxxxxxxxxxxx, rusty@xxxxxxxxxxxxxxx
- In-reply-to: <Pine.LNX.4.58.0604152323560.16853@xxxxxxxxxxxxxxxxxxx>
- References: <1145049535.1336.128.camel@xxxxxxxxxxxxxxxxxxxxx> <4440855A.7040203@xxxxxxxxxxxx> <Pine.LNX.4.58.0604151609340.11302@xxxxxxxxxxxxxxxxxxx> <4441B02D.4000405@xxxxxxxxxxxx> <Pine.LNX.4.58.0604152323560.16853@xxxxxxxxxxxxxxxxxxx>
Steven Rostedt writes:
> So now I'm asking for advice on some ideas that can be a work around to
> keep the robustness and speed.
Ideally, what I'd like to do on powerpc is to dedicate one register to
storing a per-cpu base address or offset, and be able to resolve the
offset at link time, so that per-cpu variable accesses just become a
register + offset memory access. (For modules, "link time" would be
module load time.)
We *might* be able to use some of the infrastructure that was put into
gcc and binutils to support TLS (thread local storage) to achieve
this. (See http://people.redhat.com/drepper/tls.pdf for some of the
details of that.)
Also, I've added Rusty Russell to the cc list, since he designed the
per-cpu variable stuff in the first place, and would be able to
explain the trade-offs that led to the PERCPU_ENOUGH_ROOM thing. (I
think you're discovering them as you go, though. :)
Paul.
-
: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]