Netdev List
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: netdev@vger.kernel.org, Andy Gospodarek <andy@greyhouse.net>
Cc: Daniel Borkmann <borkmann@iogearbox.net>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Jesper Dangaard Brouer <brouer@redhat.com>
Subject: [net-next PATCH 0/3] Improve xdp_monitor samples/bpf
Date: Fri, 06 Oct 2017 10:41:36 +0200	[thread overview]
Message-ID: <150727927390.4460.3200093291677318710.stgit@firesoul> (raw)

Here are some improvements to the xdp_monitor tool currently located
under samples/bpf/.  Once the tools library libbpf become more feature
complete, xdp_monitor should be converted to use it, and be moved into
tools/bpf/xdp/ or tools/xdp/.

---

Jesper Dangaard Brouer (3):
      samples/bpf: xdp_monitor first 8 bytes are not accessible by bpf
      samples/bpf: xdp_monitor also record xdp_exception tracepoint
      samples/bpf: xdp_monitor increase memory rlimit


 samples/bpf/xdp_monitor_kern.c |   60 +++++++++++++++-----
 samples/bpf/xdp_monitor_user.c |  119 +++++++++++++++++++++++++++++++---------
 2 files changed, 139 insertions(+), 40 deletions(-)

             reply	other threads:[~2017-10-06  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06  8:41 Jesper Dangaard Brouer [this message]
2017-10-06  8:41 ` [net-next PATCH 1/3] samples/bpf: xdp_monitor first 8 bytes are not accessible by bpf Jesper Dangaard Brouer
2017-10-06 16:13   ` Alexei Starovoitov
2017-10-06  8:41 ` [net-next PATCH 2/3] samples/bpf: xdp_monitor also record xdp_exception tracepoint Jesper Dangaard Brouer
2017-10-06  8:41 ` [net-next PATCH 3/3] samples/bpf: xdp_monitor increase memory rlimit Jesper Dangaard Brouer
2017-10-06 17:10 ` [net-next PATCH 0/3] Improve xdp_monitor samples/bpf David Miller

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=150727927390.4460.3200093291677318710.stgit@firesoul \
    --to=brouer@redhat.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=borkmann@iogearbox.net \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox