Bug 10795 - percpu globals
Summary: percpu globals
Status: RESOLVED WONTFIX
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-16 22:22 UTC by Josh Stone
Modified: 2017-05-09 00:13 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Stone 2009-10-16 22:22:14 UTC 
It would be nice to have global variables that are explicitly percpu.  You can
effectively to this already with a map and a cpu() index, but we could make it
completely lockless if it is a native feature.

I'm imagining this as an extension to the "global" keyword -- either as some
sort of attribute, or perhaps a new "cpu_global" keyword.  The implementation
could be simply a percpu_globals struct, or maybe even stuffed into our percpu
context struct.

We may also want {begin,end,error}.percpu probes for initializing / reporting
such globals.
Comment 1 Josh Stone 2009-10-16 22:24:55 UTC 
PR5108 is similar to this request, but I'm looking to be more generic.
Comment 2 Frank Ch. Eigler 2017-05-09 00:13:44 UTC 
people have made do with the per-cpu aggregates (<<< and @ops)