iovisor/bcc

stackcount option for stack depth limit

Open

#1,103 opened on Apr 8, 2017

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C (22,409 stars) (4,051 forks)batch import
enhancementhelp wanted

Description

Feature request for a stackcount option to limit the stack depth. Eg, "-l 5" for the top 5 frames only. get_stackid() should already support this, such that the filter and aggregation is done in kernel.

Contributor guide

Tech stack
cpython
Domain
cliobservabilityperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic C programmingPython scriptingBPF conceptsBCC codebase familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Implement a l flag in the stackcount tool. The kernel side BPF program should call get stackid with a depth limit. Modify the Python frontend to parse the l option and pass it to the BPF program. See existing examples in bcc/tools/stackcount.py and the corresponding C file. Consider how to pass the depth parameter to the BPF program via map or read from user space.
stackcount option for stack depth limit · iovisor/bcc#1103 | Good First Issue