[iccrg] 回复: New draft submitted for draft-pan-tsvwg-hpccplus-02.txt

"Rui, Miao" <miao.rui@alibaba-inc.com> Thu, 17 December 2020 02:35 UTC

Return-Path: <miao.rui@alibaba-inc.com>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664433A13AA; Wed, 16 Dec 2020 18:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FROM_EXCESS_BASE64=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATdngD_L6LO1; Wed, 16 Dec 2020 18:35:57 -0800 (PST)
Received: from out0-134.mail.aliyun.com (out0-134.mail.aliyun.com [140.205.0.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72D5D3A139D; Wed, 16 Dec 2020 18:35:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1608172552; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=/LvipuY6IJD2Kbt2sB7e78bw4V4lCwUDHUj7nsT3VF8=; b=CJH66iqyqLKs28vjlxKIgj55mCZpOjr6W4ljZ/tVAdPf/LTWnJYsWMyDt7Y0k0pdOfqFtdWkQbIFM+FyekqjSYoidbdLbnh+vX63RZM/odtu0g1JhqA2rZP4Y4RyLFipsGZkYcb4JiwfQzE6K7fbYRi4Lo+O8vgWkxEplaVEkx4=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R191e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=ay29a033018047198; MF=miao.rui@alibaba-inc.com; NM=1; PH=DW; RN=8; SR=0; TI=W4_6056262_v5ForWebDing_0A930E4A_1608171278390_o7001c3256;
Received: from WS-web (miao.rui@alibaba-inc.com[W4_6056262_v5ForWebDing_0A930E4A_1608171278390_o7001c3256]) by ay29a011140100200.et135 at Thu, 17 Dec 2020 10:35:51 +0800
Date: Thu, 17 Dec 2020 10:35:51 +0800
From: "Rui, Miao" <miao.rui@alibaba-inc.com>
To: iccrg <iccrg-bounces@irtf.org>, "Pan, Rong" <rong.pan@intel.com>
Cc: "Liu, Hongqiang(洪强)" <hongqiang.liu@alibaba-inc.com>, "jri.ietf" <jri.ietf@gmail.com>, iccrg <iccrg@irtf.org>, "Lee, Jeongkeun" <jk.lee@intel.com>, Barak Gafni <gbarak@mellanox.com>, Yuval Shpigelman <yuvals@mellanox.com>
Reply-To: "Rui, Miao" <miao.rui@alibaba-inc.com>
Message-ID: <7c4858fa-a333-4fe8-b4d1-70949e07537f.miao.rui@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent revision 5829926][W4_6056262][v5ForWebDing][Chrome]
MIME-Version: 1.0
References: <3b396b85-d412-4e52-8716-52eac2a814e8.miao.rui@alibaba-inc.com> <7ADC7D48-26A4-4446-A423-A3A6F1536B4A@ifi.uio.no> <DE4E4F61-2D63-48CA-BEF7-58FF274154CD@intel.com>, <B0C55DCA-F520-4D41-89B2-CD233821D7FF@ifi.uio.no>
x-aliyun-mail-creator: W4_6056262_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzg3LjAuNDI4MC44OCBTYWZhcmkvNTM3LjM2XQ
In-Reply-To: <B0C55DCA-F520-4D41-89B2-CD233821D7FF@ifi.uio.no>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_114129_7fbf4a4a7700_5fdac407_45b01b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/htXsI52Va2Uen1pyvEwxZ6hMOJ0>
Subject: [iccrg] 回复: New draft submitted for draft-pan-tsvwg-hpccplus-02.txt
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2020 02:36:05 -0000

Hi Michael,

Thanks for your notes. Yes, I was talking about the capacity issue with Michael Scharf in another thread. Having switch-assisted congestion control does not mean that switches need to ``allocate'' bandwidth in a dual-mode. Instead, we can still implement a primal-mode algorithm with precise congestion information provided by switches for fast utilization convergence (though it will take longer for fairness to converge).

Yes, having switch-assisted is possible with newer hardware and many vendors now support this. But we are careful about the primitives supported. 

First, in HPCC++ we only ask the switch to support write-to-packet operation which is already supported in inband telemetry (like IOAM mentioned earlier). However, IMO adding a read-from-packet operation would trigger more interesting research ideas.

Second, there are many choices of load information like tx/rx rate, qlen, timestamp, etc. The key design of HPCC++ is to define ``inflight byte'' to quantify the load, which can be calculated by tx rate, queue length, timestamp. Because inflight byte can tell both overload or underload of the link for us to increase/decrease the rate multiplicatively. On contrary, traditional wisdom of having only the queue-length as the feedback can only guide the rate decrease but not increase. Besides, it subjects to fluctuation unless a certain threshold is held. We also compare RX and TX rate as well in the paper. HPCC++ uses TX rate while XCP uses RX rate. Generally, we view the TX rate is more precise because RX rate and queue_length are overlapped and thus it causes oscillation.

Thanks,
Rui



------------------------------------------------------------------
发件人:Michael Welzl <michawe@ifi.uio.no>
发送时间:2020年12月15日(星期二) 23:11
收件人:"Pan, Rong" <rong.pan@intel.com>
抄 送:"Miao, Rui(缪睿)" <miao.rui@alibaba-inc.com>; "Liu, Hongqiang(洪强)" <hongqiang.liu@alibaba-inc.com>; jri.ietf <jri.ietf@gmail.com>; iccrg <iccrg@irtf.org>; "Lee, Jeongkeun" <jk.lee@intel.com>; Barak Gafni <gbarak@mellanox.com>; Yuval Shpigelman <yuvals@mellanox.com>
主 题:Re: [iccrg] New draft submitted for draft-pan-tsvwg-hpccplus-02.txt

Hi Rong,

On Dec 16, 2020, at 3:09 AM, Pan, Rong <rong.pan@intel.com> wrote:
Michael,

I read the paper that you referenced.

Thanks!  :-)


 Indeed, it is very similar to HPCC++.  Time has finally come to do switch-assisted congestion control 😊.

Yes, that’s what I thought when I first saw this - now there’s hardware supporting such mechanisms!


 I am not clear about your comment on “path segments”. Data center network should be able to support it end-to-end, right?

Oh sorry, is this the only context here? (It was, in the HPCC paper).  Then yes, of course!  I don’t see a problem with this for data centers.
(except for, possibly, some of the issues with “capacity" that Michael Scharf listed in his interesting email here - I see you were not in cc:
https://mailarchive.ietf.org/arch/msg/tsvwg/37SUp8JSE_tJXzKM6-tDcOhJaeA/   - but I don’t think that these *always* apply, under all conditions…  surely there must be ways around them, at least in datacenters)

Cheers,
Michael