From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (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 19D593BA8E for ; Sun, 17 Jun 2018 16:42:45 -0400 (EDT) Received: by mail-qk0-x244.google.com with SMTP id c198-v6so8353381qkg.12 for ; Sun, 17 Jun 2018 13:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=iY3Zt8LztCEP9UyGPOmaqjF4UGoSxDMOmA8xFMv0uZM=; b=JMUAqEa2X8XxbTCJvo0a+xsYXi4RbXY0rHlFSMbVYHvJcQXlKpFJqldLG+r5HQ06GQ pIteWOMotutFAf3PSLoJ8RyoAN6I/CGbI5LqCAjvx1GroKnp9v346pI+GG85YBjFWb2i D6WcJvgxWM6xRNK16qmM3luzYzMRr/6yaGGQWaWoh42teMwttY+4fdNbjKq9CE6zpb7V 7BT9/ekJPj2rUa9s5PpcvfX1wsNqBm+nLZ0oxLkHx/SzOUPL6lwCk5k6P7FvtiCiZtdX nzUV2Jb6OSZbSv6Q07kMREJF44VyERawkn4M8I7cqenIx4q+kgpi+Yd+tFcopJcorzM7 w17Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=iY3Zt8LztCEP9UyGPOmaqjF4UGoSxDMOmA8xFMv0uZM=; b=VIf0vdkkmEgBOVndcwx2eNx2Gf3J/eJ8PgOeo5TC+3AtRLHbUIGqQ2aFSm75lUUADc Kncatu2fafYYg91FWFk1S+h/XMNc5bUZvK3u2VTsRZfTqrzrm/1M4k71E2CQ6IvlDUFl 0YLg+VbrK0NxyBTMEYJrT2nicxECZ1KVsZWgTP5dfTIb/pm9nK3xNEQ99SQ2yQI0yNFs z7hb2J/DoU+PmeZ52ksf2Vc9gDyQ0My9Sy5bXgK44RIDJ+FtpKCCUVpof6UhOH0cZHQz mjWVDggq/9IX9rXtWAZvNLvtCeoniuLQxljCiy/K1JAm8j874ysEuw4lBB1hpPZPPL87 jmpw== X-Gm-Message-State: APt69E14cRSBwfrd/mP69U9G9y08Yj0kpr4IPPJ5TlJz5Qe6HsyXQy7A cjszR3etbkvXCLj2+tBp53iKQNQdGDwndGpvBuo= X-Google-Smtp-Source: ADUXVKLcKQtc3agok/vzUYQS/NGYjWaqnu3Pvtk9fKdfrCm0MMr+6zXxA3kNO+ZyJbqU4TYolLHjj2digTMBT/HlZBs= X-Received: by 2002:a37:129d:: with SMTP id 29-v6mr8091864qks.263.1529268164684; Sun, 17 Jun 2018 13:42:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:24f0:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 13:42:43 -0700 (PDT) In-Reply-To: References: <1527721073.171416827@apps.rackspace.com> <150ABF21-FAFC-48E2-9E55-CAA609EAE449@heistp.net> <20180617131921.09bf5353@redhat.com> From: Dave Taht Date: Sun, 17 Jun 2018 13:42:43 -0700 Message-ID: To: Pete Heist Cc: Jesper Dangaard Brouer , Florian Westphal , Marek Majkowski , Make-Wifi-fast Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] emulating wifi better - coupling qdiscs in netem? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 20:42:45 -0000 On Sun, Jun 17, 2018 at 11:38 AM, Pete Heist wrote: > >> On Jun 17, 2018, at 6:09 PM, Dave Taht wrote: >> >> I'm pleased that these are apu2 results, I have some hope that a >> heftier box can do better. > > I suspect 10-20x is possible on more modern, desktop class hardware. I appreciate the optimism, but it's context switch time that dominates here which does not scale. >> And these are not using the bulk verdict facility? > > It looks like not to me. nfq_nlmsg_verdict_put is called with a single ID= and I see no references to the batch verdict support there. > Presumably t= here are significant gains to be had there. But: I have high hopes for the batch verdict capability, we issue a verdict for that batch, then (wait the actual time to simulated-ly deliver an wifi aggregate - projected cpu latency), then release the next batch. this seems to me to be able to overlap and ignore the bus arbitration step almost entirely. I'll get on this myself after I'm done with the cake talk next week. Thx for the thoughts and evaluations! (still wish I could do it in-kernel) --=20 Dave T=C3=A4ht CEO, TekLibre, LLC http://www.teklibre.com Tel: 1-669-226-2619