Re: [Detnet] Terminology: queuing vs. scheduling

Hesham ElBakoury <helbakoury@gmail.com> Mon, 12 December 2022 19:27 UTC

Return-Path: <helbakoury@gmail.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8B8C1524C1 for <detnet@ietfa.amsl.com>; Mon, 12 Dec 2022 11:27:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xovmzmIMxMh8 for <detnet@ietfa.amsl.com>; Mon, 12 Dec 2022 11:27:44 -0800 (PST)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06F58C15170A for <detnet@ietf.org>; Mon, 12 Dec 2022 11:27:44 -0800 (PST)
Received: by mail-yb1-xb35.google.com with SMTP id i186so14948557ybc.9 for <detnet@ietf.org>; Mon, 12 Dec 2022 11:27:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c6RMybUwYEV0nOD572EmDC2Zf7Lv0kb0nPczZKCxfB0=; b=GfOfo+DtGigwsqMOcyRRJr/3P7rkiAaZI40pJmae/+Iu8P+pBFYEoOV4aU1LJoAlc4 sS3md8T7AWPc2fRLrS4EbwnNWh4F0LHAcUmH43CLoPrpGaNM/qfmjpNlQSFSQFSTDXWJ iXOAf5beyTcoLB8Bw51X8OystBrjOTHuL6fgoWQylXGMtA/QpsbOs3WumKxalJwp91w1 02ww21TeefAxeFcOqSYYA3PKZM3LlBtEiWm5DwoS4MUFNXeioNywhQZlkooReEc1F1wc velmjc8+0ORb5c4W7HTjlgALycm8DDPhs5XHo+LQzwHB7USa8i3tExTNDGOfC0LHm0Jn uTng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=c6RMybUwYEV0nOD572EmDC2Zf7Lv0kb0nPczZKCxfB0=; b=gG46Vrl7Rt01UPAKw+Gw/nlxe2eA0ZVXMet36MgbprfKcjbuQwuxSLVMnVzQYYa3PU aadZ8z7Tm3Ozm8BIu0LSvtjglEIEuipez2qYpr/ZuPmN+YRhrwKrDoibee6Dt6Vd3woK g9PaCfdNps5dWvJfF5oUMmCpGGXuifZIf+ncOHc4wc2d54FiXyH8fLN11+RqTRHsfuLM MgchDE7NoO1TfnqM3+stdzTtoroZwVa/rCiE7rNAHRDSh7Ki1oGRIHTRipMVde8bGiLy tUfA7Ih4lJAjphToVBjg/G6knMcdjQDp5hp+oSCn+y9IeLioKbgpNA9DaywgrPkI84Ej mhvA==
X-Gm-Message-State: ANoB5pkl9GdHe+Ax7jKhW4krKmjWWA+HxEOtHtWA/1ZbzY04Smnqb+hi /8CgLkq5W6tDKOP+l1UYvLA60V50JO9xupR2sDKTHxIR9Hfuug==
X-Google-Smtp-Source: AA0mqf5YAvYY30XpvgtBA5BUy7QzvYe+07UBOioSMcPk6FvySWBo6u+lCb2V1mkeOLWKXmYHiYKERcdu6iTejVfIjJg=
X-Received: by 2002:a25:d3c4:0:b0:6f6:ec71:8ede with SMTP id e187-20020a25d3c4000000b006f6ec718edemr45942600ybf.422.1670873262867; Mon, 12 Dec 2022 11:27:42 -0800 (PST)
MIME-Version: 1.0
References: <Y5cp49gy4vtkww+v@faui48e.informatik.uni-erlangen.de> <CO1PR11MB4881E44342A6931789606C87D8E29@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB4881E44342A6931789606C87D8E29@CO1PR11MB4881.namprd11.prod.outlook.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Mon, 12 Dec 2022 20:24:31 +0100
Message-ID: <CAFvDQ9rAXfNJsgZnjg10rsYc4QgXvt1cHw-ze2ka4eCm6MeF8g@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>
Cc: Toerless Eckert <tte@cs.fau.de>, detnet@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004c48df05efa67f2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/IFkqg2j1yDAgLQ3wTlAk2MGXrDI>
Subject: Re: [Detnet] Terminology: queuing vs. scheduling
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2022 19:27:48 -0000

This paper "Analysis and Simulation of a Fair Queueing Algorithm" (
https://dl.acm.org/doi/10.1145/75247.75248) defines queuing algorithms as
follows: "Queueing algorithms can be thought of as allocating three nearly
independent quantities: bandwidth
(which packets get transmitted), promptness (when do those packets get
transmitted), and buffer space (which packets are discarded by the
gateway). In this definition scheduling (work conserving and non-work
conserving) is part of the queuing algorithm.

Hesham

On Mon, Dec 12, 2022, 2:29 PM Pascal Thubert (pthubert) <pthubert=
40cisco.com@dmarc.ietf.org> wrote:

> Hello Toerless
>
> In my book queueing is about retention and scheduling is about a timely
> forwarding operation. But what you're looking for is about constrained as
> opposed to timely, meaning that scheduling is closer but too restrictive.
>
> All the best
>
> Pascal
>
> > -----Original Message-----
> > From: detnet <detnet-bounces@ietf.org> On Behalf Of Toerless Eckert
> > Sent: lundi 12 décembre 2022 14:17
> > To: detnet@ietf.org
> > Subject: [Detnet] Terminology: queuing vs. scheduling
> >
> > Just listening to the interim meeting, i wanted to make a side note
> > about the word we choose for our efforts:
> >
> > I have always used the term "queuing" and was often corrected by QoS,
> > TSV and other experts, who said that "queuing" is just a specific
> > internal implementation choice, but for the interoperability and
> > externally observable behavior, one should try to be as unspecific to
> > particular implementation choices as possible.
> >
> > I am not sure if there is a good single word as the name for the
> > externally observable behavior we want to define (bounded latency,
> > bounded jitter), but maybe "scheduling" is better than "queuing",
> > because it does imply the time (relative to other packets or to a
> > clock) at which a packet is being sent, and that seems to me to come
> > closest to what i think we want to define.
> >
> > Then again, i am personally quite pragmatic with names, so please do
> > not change the name of the effort on my behalf.
> >
> > Cheers
> >     Toerless
> >
> > _______________________________________________
> > detnet mailing list
> > detnet@ietf.org
> > https://www.ietf.org/mailman/listinfo/detnet
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>