Re: [Detnet] Queueing mechanism evaluation examples

Antoine FRESSANCOURT <antoine.fressancourt@huawei.com> Thu, 09 November 2023 09:49 UTC

Return-Path: <antoine.fressancourt@huawei.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 4B320C14CF05; Thu, 9 Nov 2023 01:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 snRzCY_d3Y6N; Thu, 9 Nov 2023 01:49:11 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A27AC14F739; Thu, 9 Nov 2023 01:49:11 -0800 (PST)
Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SQxw518cwz6K7Jp; Thu, 9 Nov 2023 17:48:05 +0800 (CST)
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Thu, 9 Nov 2023 09:49:09 +0000
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2507.031; Thu, 9 Nov 2023 09:49:09 +0000
From: Antoine FRESSANCOURT <antoine.fressancourt@huawei.com>
To: Jinoo Joung <jjoung@smu.ac.kr>, "peng.shaofu@zte.com.cn" <peng.shaofu@zte.com.cn>
CC: "detnet@ietf.org" <detnet@ietf.org>, "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>, "david.black@dell.com" <david.black@dell.com>
Thread-Topic: [Detnet] Queueing mechanism evaluation examples
Thread-Index: AQHaErrPRkrBtQtcREWsjaB2qGJSM7BxYrcAgABbTSA=
Date: Thu, 09 Nov 2023 09:49:09 +0000
Message-ID: <814d6e5c5ab14c62bda709b3098e99a1@huawei.com>
References: <202311091111142024189@zte.com.cn> <CA+8ZkcSLhyhBhNnA-jEuquBeEBQfyyOmbKYjZTiv-VvbryB7bQ@mail.gmail.com>
In-Reply-To: <CA+8ZkcSLhyhBhNnA-jEuquBeEBQfyyOmbKYjZTiv-VvbryB7bQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.70.189]
Content-Type: multipart/alternative; boundary="_000_814d6e5c5ab14c62bda709b3098e99a1huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/H2mGHOU_DSCNnwL5WUVtX9b9r74>
Subject: Re: [Detnet] Queueing mechanism evaluation examples
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: Thu, 09 Nov 2023 09:49:16 -0000

Hello Jinoo,

Thanks for the reference to your article, I will read it carefully before trying to compute end to end delay bounds for the bounded queue delay mechanism following a similar approach with my colleagues.

Best regards,

Antoine

From: detnet <detnet-bounces@ietf.org> On Behalf Of Jinoo Joung
Sent: jeudi 9 novembre 2023 05:21
To: peng.shaofu@zte.com.cn
Cc: detnet@ietf.org; detnet-chairs@ietf.org; david.black@dell.com
Subject: Re: [Detnet] Queueing mechanism evaluation examples

Shofu, thanks for the suggestion.

Your scenario seems to contain only a single hop with the flows of monotonically increasing latency bounds specifications.
I suggest that for a scenario to be effective in evaluating our queuing solutions, the following requirements should be met.

1. The network should have a large enough diameter, such as more than 8 hops or so.
2. The network should have a complex topology including mesh or ring.
3. The flows should have TSpecs, including max burst size and average rate.
4. The flows should have RSpecs, which reflect realistic latency & jitter bounds such as those of video, XR gaming, or industrial control loop.

My paper below has the simulation setup which meets these requirements.
If you are interested, please take a look.

Joung J., Kwon J., Ryoo J-D., Cheung T., "Scalable flow isolation with work conserving stateless core fair queuing for deterministic networking" IEEE Access, vol. 11, Sep. 2023. doi: 0.1109/ACCESS.2023.3318479

Best regards,
Jinoo

On Thu, Nov 9, 2023 at 12:11 PM <peng.shaofu@zte.com.cn<mailto:peng.shaofu@zte.com.cn>> wrote:



Hi WG,



During the session, most people hope to have one or several common examples to evaluate various queueing mechanisms.

I provided an initial example (see the attachement).

Hope it can be helpful and welcome more examples with typical and real requirements can be added.





Regards,

PSF


_______________________________________________
detnet mailing list
detnet@ietf.org<mailto:detnet@ietf.org>
https://www.ietf.org/mailman/listinfo/detnet