From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D84753B29E for ; Sun, 28 Apr 2019 20:17:53 -0400 (EDT) Received: by mail-lf1-x132.google.com with SMTP id h18so6422615lfj.11 for ; Sun, 28 Apr 2019 17:17:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=X7LLiL9VkheFasBWJ4o2EyhpIS8FJ+WA5j8fc2Ww+1g=; b=uJbYbpj36twMLQmsgIcnADi3Tz722JD8NGXjWJX2UGb+GoKTBk/+aDNmEPIwnftiQY 8xUq9dls71J2wtlrigj9eoE3XakgVLB5gZZ9w7CYXYN5wMrpATuZSiwWO1aivfPXZ8Ir VR2RcYrTT5kWD6lzB1CFx5R+J2z0v+3oWRNrGR/hvl2Ppio4oAYQU6YeWpblrBa4h9Ry g8NTZ+LXANbqnCCKyjrqIlYOlVg1nYSa3mefdexPRZNwgiE6PkuCe5I6Z44MjBy7ZXyR 3bYalYY6k8n7Cs9KAbEN4jJgiavgc7ZFRhg7NLAwtarDc7IHPhU6Jh46AsdYwNMp7MW8 xoQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=X7LLiL9VkheFasBWJ4o2EyhpIS8FJ+WA5j8fc2Ww+1g=; b=NvY7B7XTO8Z4Jv6y+nsiJDz3qJ5zPrOiM4VqomkOKinRq4znBL6XYGLqGAYkABAk9o uvofCV2168IizzO+4TAkui/4ipE1dZEdELt4b5FPbAAJxqU0m0XVXUfKBPING2gMzmfP JezaMvrm5gRhAI9qk914yy6TP21ehXXSSb6LY/6oinGQOqT7Nm6nf1IRRbxj3im4Qh4n ivPLjCq68YCVOBWxIWloIrRtVrFo1RxllVJQitl+im/VzQqOww/yMIKj4erejR39IV0f 9s3gfLOqTQM3Mbzh258xUWWOTo5lFY2FS5XqkfBNgtrpFCJBNI38wt7RlZTxDKxXhhzb FJgA== X-Gm-Message-State: APjAAAX6hZZuVbjKrPa7PdXmWRz0bnAXA3NVHGjtrs1TkXXBoyWGEw3u LJGNNlFInUiwYYLv45V2lOM= X-Google-Smtp-Source: APXvYqxqKUw2vuHYXIwfSY6PMQrX8QHyyeDHC55NGCtITR7SEYTTNraIPg/UL87QJUvdjXWGASDe6Q== X-Received: by 2002:a19:7d04:: with SMTP id y4mr13234979lfc.153.1556497072507; Sun, 28 Apr 2019 17:17:52 -0700 (PDT) Received: from jonathartonsmbp.lan (83-245-240-147-nat-p.elisa-mobile.fi. [83.245.240.147]) by smtp.gmail.com with ESMTPSA id k4sm3472763lja.18.2019.04.28.17.17.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Apr 2019 17:17:52 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Jonathan Morton In-Reply-To: Date: Mon, 29 Apr 2019 03:17:50 +0300 Cc: Cake List Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Shefali Gupta X-Mailer: Apple Mail (2.3445.9.1) Subject: Re: [Cake] Testing Scenarios for Validation of Ack_Filter implementation in ns-3 X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 00:17:54 -0000 > On 22 Apr, 2019, at 2:45 pm, Shefali Gupta = wrote: >=20 > It would really help if you could suggest the testing scenarios so = that I can validate Ack_Filter implementation in ns-3. It may help to understand the design intentions of the ack-filter: 1: Reduce the bandwidth consumed by pure acks, and possibly also the = latency of the ack stream. 2: Avoid losing any relevant information from the ack stream. This = particularly includes not erasing any "tail" acks and not interfering = with any SYN, FIN or RST packets. To test the latter, you really need a correctness analysis, but it = should be sufficient to observe no reduction in performance across a = wide range of scenarios, including those involving application-limited = workloads (with a lot of tail acks), many short flow starts, continuous = transfers with various amounts of packet loss in the forward direction, = and cases where ack-filter activity is intense. That last scenario will involve a demonstration of point 1, which is = best achieved by setting up an asymmetric link, then running one flow = over the "wide" direction but many flows over the "narrow" direction. A = 10:1 bandwidth ratio with a 1:50 flow setup should do the trick. The = ack filter should greatly improve the throughput of the single, fast = flow, and also free up a little bandwidth on the slow side for the many = flows. As an aside, in the current Cake version we treat the former NS bit the = same way as the ECE and CWR bits in the ack filter, so you may want to = ensure this tweak is also made in your version. This is to improve its = behaviour on SCE traffic. The change should have no effect on non-SCE = traffic. - Jonathan Morton