From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 CFD9C3CB37 for ; Wed, 13 Feb 2019 14:26:35 -0500 (EST) Received: by mail-qt1-x836.google.com with SMTP id a48so4024129qtb.4 for ; Wed, 13 Feb 2019 11:26:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=u5h4opxVmYw08N6GG6mcYdD/rkmtDhQlfBtIuxn+cRw=; b=laejOPzkJEGb2u2fY8m0wYhvyEmQL9lkdH3w5YeeAFZcIgvkYwhJ306cWZ2Srpm3Qe FUQdK50N491HYMfQ5pW25vh6rwqY2Kt/PX8kgd0p8b7rNqrpDiChAAaRGpMDJoEtR6NA sycP9b2GJdMLJ3KkVHbAk3yRKoUF6qVKoXU3/ogXep139RpDRyIX3AhuQhs3bFQtMqV1 ug6zwMebCeck1XFCSQLedjuvgGQ1A729WdPf7zzbMMHXXbiJv8s/rl0p8atcJZmpzhCY 067b0GQ7La55AI7FIsY4DCDgNaSnP88mty+chqdBpo4uduoRjjeaGlziDqvxJ9iT3hKM mrVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:content-language :thread-index; bh=u5h4opxVmYw08N6GG6mcYdD/rkmtDhQlfBtIuxn+cRw=; b=atBleKuANDT2eTiCOfsosf2gQ6LfLaLACNnGCmSGKMcCi8cY2jgyosJDvIDZPoVl0k ZypQj/mX0RhElA9BoWp6Z+9rQq+it3GbxdIzYdyy61WLNzdEpaH6bzmrXTHNtAsuA00z K5HdpVoscFW/+9ycdocOD897PjgEqKQCQqHEYrB1aygJ8lVrFyCzh8rQEcXeLnuaYSKk qQ7S+xOZiS61A4gXa4U0pT1W93V/C5PCureWiu6KKe1ps1tZ+gDHqAnv/upe5+Z8qOv7 Me4EAbVDVtShi6FSrcBMr2h8cWj7mb3qpIvq/lFs2IucDWyl1wSpMe3DzDylTRG4TDAM RQCw== X-Gm-Message-State: AHQUAubKWHome05m9iMDJH2fStrfuNYR0EsNsn1TV/iQ81enxLIY4H22 buQYbOTQYWZPAJ7VvPQ/2DN3Oq1dkSE= X-Google-Smtp-Source: AHgI3IbwY3HQ/MyNKCsJ8iVSS1tj83W1OAb/wSjbMliQtSkB5sNNBOhx2S4XB1xkmjeg13t5pX5xvQ== X-Received: by 2002:ac8:962:: with SMTP id z31mr1738672qth.305.1550085994764; Wed, 13 Feb 2019 11:26:34 -0800 (PST) Received: from DESKTOPV0UVPFT ([2601:152:4302:ae1f:6159:382c:f3e2:3da3]) by smtp.gmail.com with ESMTPSA id p17sm93574qtk.39.2019.02.13.11.26.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 11:26:34 -0800 (PST) From: To: "'Jonathan Morton'" Cc: , References: <20190213183132.11019-1-gamanakis@gmail.com> <144BF042-D64B-45D2-BF48-16FD7AE67411@gmail.com> In-Reply-To: <144BF042-D64B-45D2-BF48-16FD7AE67411@gmail.com> Date: Wed, 13 Feb 2019 14:26:35 -0500 Message-ID: <006b01d4c3d2$090c3350$1b2499f0$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQILPQk8abJn24CFhbMR+/fQyyXfSgJDcYtGAtrOiImlSDdS8A== Subject: Re: [Cake] progress? dual-src/dsthost unfairness 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: Wed, 13 Feb 2019 19:26:35 -0000 >1: Why is host_load calculated using host_sparse_flow_count instead of host_bulk_flow_count in cake_enqueue()? Because the flow for which cake_enqueue() is run is by definition a sparse one. So the host_load should be adjusted according to the sparse flow count for the particular host. That's my reasoning behing this, would be happy to hear other opinions. >2: Do we actually need to maintain host_sparse_flow_count at all, or only the bulk one? If the above is corrected, I don't think there are any uses left. See above. George