Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jarad Olson <brotherdust@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Latency Testing Using iOAM
Date: Sun, 8 May 2022 08:31:27 -0600	[thread overview]
Message-ID: <1FEEA029-B564-4C46-99A7-50B5F747F619@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

Hello!
Has anyone ever tried using in-situ OAM for testing latency? It would seem to me that the protocol is ideal for this purpose: it adds metadata to actual user packets. The Linux kernel has support for it as of 5.15, Cisco and Juniper have implemented it as well.

Here’s an article on the Linux kernel implementation: https://legacy.netdevconf.info/0x14/pub/papers/32/0x14-paper32-talk-paper.pdf

If anyone has tried this, how did it turn out?

Thanks much!

[-- Attachment #2: Type: text/html, Size: 761 bytes --]

             reply	other threads:[~2022-05-08 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 14:31 Jarad Olson [this message]
2022-05-13 17:06 ` Dave Taht

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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=1FEEA029-B564-4C46-99A7-50B5F747F619@gmail.com \
    --to=brotherdust@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    /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