[RFC PATCH v8 0/9] Restartable sequences system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 2/9] tracing: instrument restartable sequences · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 3/9] Restartable sequences: ARM 32 architecture support · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 4/9] Restartable sequences: wire up ARM 32 system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 6/9] Restartable sequences: wire up x86 32/64 system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 9/9] Restartable sequences: self-tests · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 5/9] Restartable sequences: x86 32/64 architecture support · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 7/9] Restartable sequences: powerpc architecture support · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 8/9] Restartable sequences: Wire up powerpc system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
[RFC PATCH v8 1/9] Restartable sequences system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Linus Torvalds <torvalds@linux-foundation.org> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Josh Triplett <josh@joshtriplett.org> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Linus Torvalds <torvalds@linux-foundation.org> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Andi Kleen <hidden> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Paul E. McKenney <hidden> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Linus Torvalds <torvalds@linux-foundation.org> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Paul E. McKenney <hidden> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Josh Triplett <josh@joshtriplett.org> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Dave Watson <hidden> · 2016-08-19
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-25
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Ben Maurer <hidden> · 2016-08-25
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Josh Triplett <josh@joshtriplett.org> · 2016-08-27
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Mathieu Desnoyers <mathieu.desnoyers@efficios.com> · 2016-08-29
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Josh Triplett <josh@joshtriplett.org> · 2016-08-29
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Boqun Feng <hidden> · 2016-08-30
Re: [RFC PATCH v8 1/9] Restartable sequences system call · Pavel Machek <hidden> · 2016-11-26

Re: [RFC PATCH v8 1/9] Restartable sequences system call

From: Andi Kleen <hidden>
Date: 2016-08-19 20:56:17
Also in: lkml

Nobody gets a cpu number just to get a cpu number - it's not a useful
thing to benchmark. What does getcpu() so much that we care?

malloc is the primary target I believe. Saves lots of memory to keep
caches per CPU rather than per thread.

-Andi

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help