Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Fwd: Pie not fully implementable on tofino p4
Date: Wed, 23 Jun 2021 13:02:38 -0700	[thread overview]
Message-ID: <CAA93jw5ysxtsTnJUrtQYWc95s-h5pGMd1+PSpe4Kmjy_SamkEw@mail.gmail.com> (raw)
In-Reply-To: <0e2c44fc-85ee-8be8-5f6b-1a71141cf07f@kom.tu-darmstadt.de>

One of the things that has long bugged me about the p4 spec was the
lack of an invsqrt which is a single assembly language instruction or
about 3k gates, for a newton approximation.

Anyway, I wish I had direct comparison data for pie vs codel on p4,
two good papers below.

---------- Forwarded message ---------
From: Ralf Kundel <ralf.kundel@kom.tu-darmstadt.de>
Date: Wed, Apr 21, 2021 at 9:07 AM
Subject: Re: Pie not fully implementable on tofino p4
To: Dave Taht <dave.taht@gmail.com>, bloat
<bloat@lists.bufferbloat.net>, <codel@lists.bufferbloat.net>


Hi,

regarding the question: how timestamps come from ingress to egress pipe?

Well this depends (on the P4 abstraction) on the P4 version you use. As
far as I remember (it is a long time ago) in P4_14 metadata (which can
store the timestamp) are handed over implicitly from ingress to egress.
In P4_16 you have do do this explicitly in the Deparser of Ingress and
Parser of Egress: Simply said you just write the timestamp before the
Ethernet header. You can see this here in line 64 to 80:
https://github.com/ralfkundel/p4-codel/blob/master/targets/tofino/srcP4/l1switchCodel.p4


best,
Ralf

Am 21.04.21 um 04:42 schrieb Dave Taht:
> https://www.comsys.rwth-aachen.de/fileadmin/papers/2021/2021-kunze-aqm-tofino-p4.pdf
>
> For a codel comparison, see:
>
> https://arxiv.org/pdf/2010.04528v1.pdf
>
> Where the authors show that fq_codel is feasible on the PISA platform...
>
> but a direct comparison between the two papers is not possible. What I
> don't understand about the above paper is how codel timestamps are
> passed from ingress to egress.
>
--
________________________________________________

Ralf Kundel, M.Sc.

Technical University of Darmstadt
Dept. of Electrical Engineering and Information Technology Multimedia
Communications Lab (KOM)
Adaptive Communication Systems Group (ACS)

Postal address: TU Darmstadt, FB 18, KOM, Rundeturmstr. 10, 64283
Darmstadt, Germany
Location: S3|20 - 216
Tel: +49 6151 16-20855
Email: Ralf.Kundel@kom.tu-darmstadt.de
Web: http://www.kom.tu-darmstadt.de
___________________________________________________________



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

           reply	other threads:[~2021-06-23 20:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <0e2c44fc-85ee-8be8-5f6b-1a71141cf07f@kom.tu-darmstadt.de>]

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

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

  git send-email \
    --in-reply-to=CAA93jw5ysxtsTnJUrtQYWc95s-h5pGMd1+PSpe4Kmjy_SamkEw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=starlink@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