CoDel AQM discussions
 help / color / mirror / Atom feed
From: Luca Muscariello <muscariello@ieee.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, starlink@lists.bufferbloat.net
Subject: Re: [Codel] Finite-Buffer M/G/1 Queues with Time and Space Priorities
Date: Wed, 27 Jul 2022 19:23:34 +0200	[thread overview]
Message-ID: <CAH8sseRtqMzfF8jDJpXtqreAJa83fPezo4fsciZ9r+Si8z2a1Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Q20SexP2w1SG5U0D+x2TVWNkNXCvghLQXd95b=8dAyA@mail.gmail.com>

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

On Wed 27 Jul 2022 at 17:34, Dave Taht <dave.taht@gmail.com> wrote:

> Occasionally I pass along a recent paper that I don't understand in
> the hope that someone can enlighten me.
> This is one of those occasions, where I am trying to leverage what I
> understand of existing FQ-codel behaviors against real traffic.



I’m not sure how realistic the model is. The delay-sensitive class gets
non-preemptive service prioritization over the loss-sensitive class (
dequeue time) So far so good.
The loss-sensitive class can take advantage of the presence of
delay-sensitive packets in the queue at enqueue time if the buffer is full
by dropping delay sensitive traffic.

I don’t think it models anything useful for fq-codel.
It might be a model for loss-less networks  like fiber channel or things
like NVMe over  Fabric with Ethernet as fabric.


>
> https://www.hindawi.com/journals/mpe/2022/4539940/
>
> Compared to the previous study on finite-buffer M/M/1 priority queues
> with time and space priority, where service times are identical and
> exponentially distributed for both types of traffic, in our model we
> assume that service times are different and are generally distributed
> for different types of traffic. As a result, our model is more
> suitable for the performance analysis of communication systems
> accommodating multiple types of traffic with different service-time
> distributions. For the proposed queueing model, we derive the
> queue-length distributions, loss probabilities, and mean waiting times
> of both types of traffic, as well as the push-out probability of
> delay-sensitive traffic.
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
>

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

  reply	other threads:[~2022-07-27 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 15:34 Dave Taht
2022-07-27 17:23 ` Luca Muscariello [this message]
     [not found] ` <ae7a9f3e-6f94-1953-20dd-3d2140a4e49d@kit.edu>
     [not found]   ` <CAKf5G6L8_sKGtSQ-0RaiQdTkwd=7shjtKi9HKq0k+D+SXGu0=w@mail.gmail.com>
2022-07-28  9:55     ` [Codel] [Starlink] " Sebastian Moeller
     [not found]       ` <CAKf5G6L86pXFj7s-gB1VfiF3gctDpbd7Biw6mKhLfxXgRTRSzA@mail.gmail.com>
2022-07-28 13:50         ` Dave Taht
2022-07-29 14:55           ` Dave Taht
2022-07-29 15:29             ` Sebastian Moeller
2022-07-29 17:08               ` Dave Taht
2022-07-29 17:41                 ` Sebastian Moeller
2022-07-29 15:29             ` Sebastian Moeller

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

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

  git send-email \
    --in-reply-to=CAH8sseRtqMzfF8jDJpXtqreAJa83fPezo4fsciZ9r+Si8z2a1Q@mail.gmail.com \
    --to=muscariello@ieee.org \
    --cc=codel@lists.bufferbloat.net \
    --cc=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