From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 66BF93BA8E for ; Mon, 3 Sep 2018 09:00:14 -0400 (EDT) Received: by mail-lj1-x232.google.com with SMTP id m84-v6so387150lje.10 for ; Mon, 03 Sep 2018 06:00:14 -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=apNXWr3Z9KDAOucymL0wGq8hGZHw88YFUE4hiMA8n6U=; b=a68d1IPd8PXkf1TwpODXUHi3PZgiuMlK4FdxNbnRoyfunOsqsK43OBdQfXLeyPl+He YrsrEHmCF/bNgrFs9aEdQag6+SznD7Kp0XU/iGl3lqZiSRUpEdEUSzza5s4KgnGes2E0 W9S1cmc6iwOQmHXLtcHlnQM94LhwrKdc2s5v/PunbVHtruyaN3bcyEn68URv5VlMDxCt pXsGYat+/xvA6Xf8vafMyvEZGfPpeDKKBK6rSSvKJUEYdSywfMhSevn9C/7prvulJPzL ZqC8G7Q14m/tsSpXkvbIx3tpnJ1BgfRtd2Do66MlY/XQlm0Jq5BrxLUdeCeCKarGU5gZ Zufg== 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=apNXWr3Z9KDAOucymL0wGq8hGZHw88YFUE4hiMA8n6U=; b=HN7/F4/skcg6KAZqA8mfGCRCjvS93CbHERNt1csdHNq59fJqqcwwm1ANkMXF+dnBAh cAc8f94NIHo5IO8UQClB+r7B1xK/IoCSd5abI1msP8pJWrLOsvwJ4WYz4KFj/HgBOYas rq9XppGIQDyQgPFTBEGzOd84AHN18yuYzJ1wjDfClVc8B4Vo5AuMR8c3KWDKeHWIs2qe p9j1ldg5941ihE+HP1qSTFQjdCBHv4/ddBLnplrXDkEW1ttPXomzKIfpJIS+w72Ge3hB yOB2ZiyhWXbkY9pV8CkU/gVvl+qDfQ4gCQ3VneNI0Nd6TrTtCLwfyAbeYFOLGEZU/rWy cyTg== X-Gm-Message-State: APzg51DWqWGnm/6amTL/B3i7x6ztncYDAWJbzi0H1sH081B5wuNuPN17 Fe9iKEQtDb9c98lN7/bQ6/o= X-Google-Smtp-Source: ANB0Vdb2B2gVGLRzO5cUl6szAy26OlD6fsKseL7+e2PIwhoM38rRcsCAbOR2h9umkPxlPxzCwoGITQ== X-Received: by 2002:a2e:9c4d:: with SMTP id t13-v6mr16920599ljj.153.1535979613345; Mon, 03 Sep 2018 06:00:13 -0700 (PDT) Received: from jonathartonsmbp.lan (83-245-237-1-nat-p.elisa-mobile.fi. [83.245.237.1]) by smtp.gmail.com with ESMTPSA id 96-v6sm3594349lfu.40.2018.09.03.06.00.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Sep 2018 06:00:12 -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, 3 Sep 2018 16:00:10 +0300 Cc: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= , Cake List Content-Transfer-Encoding: quoted-printable Message-Id: References: <87ftyq25q0.fsf@toke.dk> <44155B82-EEFA-4769-AD95-5D17EC677905@gmail.com> To: David Lang X-Mailer: Apple Mail (2.3445.9.1) Subject: Re: [Cake] arp flow dissector 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, 03 Sep 2018 13:00:14 -0000 > On 3 Sep, 2018, at 3:29 pm, David Lang wrote: >=20 > how much ARP traffic would there have to be before the benefits of = this outweigh the overhead of tracking it? If there's very little ARP traffic (as normal), then the overhead of = recognising it is basically nil. The benefits become apparent as soon as the volume of ARP traffic, in = aggregate, becomes great enough for its queue to be marked "saturating" = instead of "sparse". This could reasonably occur if the other traffic = consists of a lot of distinct flows. - Jonathan Morton