General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>,
	brouer@redhat.com,
	"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Subject: Re: [Bloat] one big bump in the wire for latency monitoring
Date: Fri, 26 Jan 2018 09:50:21 +0100	[thread overview]
Message-ID: <20180126095021.4d7de9aa@redhat.com> (raw)
In-Reply-To: <877es51t6y.fsf@toke.dk>

On Thu, 25 Jan 2018 23:15:17 +0100
Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Dave Taht <dave.taht@gmail.com> writes:
> 
> > https://blog.apnic.net/2018/01/22/ruru-real-time-wide-area-tcp-latency-monitoring/  
> 
> Neat! The packet tapping part could probably be implemented in XDP to
> avoid the DPDK space heater... ;)

I was thinking the exact same thing ;-)

It should be fairly simple to write a XDP/eBPF program, that timestamp
via bpf_ktime_get_ns() and queue the events via a perf ring-buffer via
bpf_perf_event_output() (the only kernel example is [1]). And a
userspace side tool[2] that reads these perf_event's.

Cc. xdp-newbies@vger.kernel.org hoping someone want to give it a go?

[1] https://github.com/torvalds/linux/blob/master/samples/bpf/trace_output_kern.c
[2] https://github.com/torvalds/linux/blob/master/samples/bpf/trace_output_user.c
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

      reply	other threads:[~2018-01-26  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 20:00 Dave Taht
2018-01-25 22:15 ` Toke Høiland-Jørgensen
2018-01-26  8:50   ` Jesper Dangaard Brouer [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180126095021.4d7de9aa@redhat.com \
    --to=brouer@redhat.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=toke@toke.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox