public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Serhei Makarov <serhei@fastmail.com>, systemtap@sourceware.org
Subject: Re: stap/eBPF language features brainstorm
Date: Thu, 19 Jul 2018 15:27:00 -0000	[thread overview]
Message-ID: <01c4f735-68b0-7d0b-11bf-0c89523839ca@redhat.com> (raw)
In-Reply-To: <1531340017.1855006.1437712520.41D1C30F@webmail.messagingengine.com>

On 07/11/2018 04:13 PM, Serhei Makarov wrote:
> Some very rough ideas on how to jam further desirable SystemTap language features into the constraints of eBPF. The goal isn't for total feature-parity with the kernel backend (that's not feasible) but for the restrictions to be clear and understandable, e.g.:

... 
> - Certain operations (e.g. foreach) can only be done in userspace. It's clearly documented which probes run in userspace (e.g. begin, end, selected ?timer probes).

A number of the systemtap script have idioms like the following from iotop.stp:

global io_stat,device
global read_bytes,write_bytes

...

probe timer.ms(5000) {
  /* write out data */
  /* clear data */
  delete io_stat
  delete device
  read_bytes = 0
  write_bytes = 0  
}

Is there some way to clear out all the previous entries in the bpf map from the timer probe?

-Will

  parent reply	other threads:[~2018-07-19 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 20:13 Serhei Makarov
2018-07-12 15:47 ` Serhei Makarov
2018-07-19 15:27 ` William Cohen [this message]
2018-07-19 17:32   ` Serhei Makarov
2018-07-19 17:56     ` William Cohen

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=01c4f735-68b0-7d0b-11bf-0c89523839ca@redhat.com \
    --to=wcohen@redhat.com \
    --cc=serhei@fastmail.com \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).