All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kubakici@wp.pl>
To: xdp-newbies@vger.kernel.org
Subject: XDP/BPF C and python libraries?
Date: Thu, 20 Jul 2017 22:53:08 -0700	[thread overview]
Message-ID: <20170720225308.14e2ac14@cakuba.netronome.com> (raw)

Hi!

I've been writing various cli programs and little tools to play with
XDP and maps lately (testing NFP map offload).  I have a simple CLI
for loading programs, setting XDP up and interacting with maps.  It's
based on libbpf from tools/ and the loader from samples/bpf.  I wonder
how do others perform basic map interactions?  Perhaps I'm approaching
the problem from the wrong side?  Is anyone working on command line
interface for simple update/dump/delete operations?

I think it's recommended to use bpffs, are there any tools for
interacting with it?

Are there any Python libraries which could take care of parsing ELF
files and poking maps?  My understanding is that BCC is not really the
tool for the job, because it's too high-level.  I don't want to compile
programs each time I want to load them.

On the kernel sources - I'm pretty sure this was discussed on netdev
but I forgot the conclusion :( - is it possible to move
samples/bpf/bpf_load.c in some form to libbpf?

             reply	other threads:[~2017-07-21  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21  5:53 Jakub Kicinski [this message]
2017-07-21 10:22 ` XDP/BPF C and python libraries? Daniel Borkmann
2017-07-21 22:37   ` Jakub Kicinski
2017-07-22  7:20     ` Jakub Kicinski
2017-07-23  5:35       ` Y Song
2017-07-23 23:54       ` Jakub Kicinski
2017-07-24  0:27         ` David Ahern
2017-07-24  1:00           ` Jakub Kicinski
2017-08-04 22:20       ` David Ahern
2017-08-05 16:40         ` Jakub Kicinski
2017-08-05 19:59           ` David Ahern

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=20170720225308.14e2ac14@cakuba.netronome.com \
    --to=kubakici@wp.pl \
    --cc=xdp-newbies@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.