From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 4D02D3B343 for ; Fri, 15 Apr 2016 07:42:00 -0400 (EDT) Received: by mail-lf0-x236.google.com with SMTP id j11so141868835lfb.1 for ; Fri, 15 Apr 2016 04:42:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=V0vbECmRDxlsoD/2A5I3TeH5+X9dMwT7LiBUm3yqMmA=; b=HQFKMLFHecoY93SlvxNdYIstDFtSkzdK6+9+Q0vN23TII2bdbMrPSwapdkrR+4Wvc1 o42jz3n8mNmloDyU42qOEKq3sqX1IJubsf2MKWzzCc2e+anRfctvwvRJsPnYMX1OcD0U FE1fUF3bwBAfrnhZq1pOvz7yzQDRSlNLsEHVAN8qQLmECEkX+Aw1EnqcEWpm5xchytEX fOdAzxUfht6YJn4bpMouKssteA4q44ok48lI+N5UNci7US8KhciX7ripCgqynwIBcQl2 4SNcbXQ8c9hdEUEphwHY3opm3swuTJE3Jl2XkOsJSULLXFjAfEUQpavmISJETJ30IF2T dP4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=V0vbECmRDxlsoD/2A5I3TeH5+X9dMwT7LiBUm3yqMmA=; b=YkjTFJ3TNTpsPnt7wa4S82bA0vmFQHEYcPrlBv2SpJSeGfzkLJfWHhCR2LG5HkjYXN 5dFlcIlc68jvitcYDV2coi1E2X9KuYiVtvT1rV0xe6M0Seg7PKZdQ0lMn3kP1EB9FXfW wGCh1Amr15I1zfluLC3jk9HVbl7xfu2yM9fIZzAPx3RmQR3Z11Vjli5Z8zlmA/mvvP2q ee7p6RSOaupcHPnS1x+SitbWM1YCSF7JFDyeHu5LL5+WFW2/8oxDC0KXpx0XAxAP7p4L jtsACmLJ6nCux02bMcc90E1AnCcfMvSXmKN2IcoTX42TQg7npUGY/Nkc1EtPLKT5sUqS Q53A== X-Gm-Message-State: AOPr4FURjzsdgjGSyayKF/KfSaF5Sj9i+PwKkZ2PdS36IftnN9Bkk7PwdB2SfWnwLU1Uig== X-Received: by 10.112.219.101 with SMTP id pn5mr8268751lbc.62.1460720518959; Fri, 15 Apr 2016 04:41:58 -0700 (PDT) Received: from bass.home.chromatix.fi (37-33-67-252.bb.dnainternet.fi. [37.33.67.252]) by smtp.gmail.com with ESMTPSA id m35sm7452117lfi.25.2016.04.15.04.41.53 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2016 04:41:57 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Jonathan Morton In-Reply-To: Date: Fri, 15 Apr 2016 14:41:42 +0300 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Henning Rogge X-Mailer: Apple Mail (2.3124) Subject: Re: [Cake] Cake in userspace 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: Fri, 15 Apr 2016 11:42:00 -0000 > On 15 Apr, 2016, at 14:02, Henning Rogge wrote: >=20 > How difficult would it be to implement Cake directly in Userspace > behind a TAP device (that you always drain of all incoming packets)? Cake relies on a number of kernel services, which would need to be = replaced. This would also be true for a port to a different kernel, = such as BSD - a question which has already occurred. The most troublesome of these services would probably be the packet = dissector, which is used to identify the 5-tuple for flow isolation. = The rest is largely standard entry points, timer services, memory = management, and configuration. My advice is to rip out the kernel-specific headers, try to compile it, = and see how loudly the compiler complains. :-) - Jonathan Morton