From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16A06C47E49 for ; Tue, 29 Oct 2019 08:56:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E016E20873 for ; Tue, 29 Oct 2019 08:56:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=cloudflare.com header.i=@cloudflare.com header.b="od2P2y/7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730226AbfJ2I4c (ORCPT ); Tue, 29 Oct 2019 04:56:32 -0400 Received: from mail-lf1-f65.google.com ([209.85.167.65]:43582 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730215AbfJ2I4c (ORCPT ); Tue, 29 Oct 2019 04:56:32 -0400 Received: by mail-lf1-f65.google.com with SMTP id j5so3529779lfh.10 for ; Tue, 29 Oct 2019 01:56:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=0est3ShahLxcPmw4Tsar7U28jeB8H6MurigDJXjbStw=; b=od2P2y/7xCpqSD19BaWaLFMB+5Gsrg2etCnIdR1Nn2xujiCDMq7Fcz5unWkRCbnKBp HMxWukdHd+mVeCpVYqZkmTaDLx7a3+vWTcWVVzgpLL79yCq+MiGrcFv9Qs71Icf0Fz3r v06eTz2PV/dw9FDorCGG07Af0RxSBhDpTOOco= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=0est3ShahLxcPmw4Tsar7U28jeB8H6MurigDJXjbStw=; b=A5voma/Z/51rJrtDa1sj7+Ue4Ns2VfPmt0iyBQ7jjCrgAtOUxrX6/xlQ1P0XB5V0WJ GvrJ8mT67iKSDVy6F5GcG/IQRudWjtXSJ+7Esn9Ov5XtHkoMXkAKHultyK/DHVAK0/6P fpZdGHnpoULkBGTJb4RrT1p5oNiTg56mgv9uu8ZL6V69tT4MqmnpGdtXfQ8EdF7kMsts nsip2x0y1ThjQ8fxwQIObyu5PYqE7aMqhTCv1rNLSkQWmkNtND2qAfLwJ+MSGbuC1CDJ UchdMK6vVP1VJNBqWSXEow3O6LpwSQS2wBEF975bMSJ4pMkWe7NIv7bDlMH/wefs6QcN xqZA== X-Gm-Message-State: APjAAAUSBu/+40whYo0T2rHEtzIdHFBAQHrdS6hpMbnT1h5NcXefK3pe X/t9CpAvspV22ZfxNIZMiWZrVQ== X-Google-Smtp-Source: APXvYqzpE2JaFYk5lUazrtMmZ9MfYwsYj+VZDhqYHEYTt4fWG5wpFvuG2s3HMzUlZGKMRqvQHRd49g== X-Received: by 2002:a19:98e:: with SMTP id 136mr1560765lfj.27.1572339390258; Tue, 29 Oct 2019 01:56:30 -0700 (PDT) Received: from cloudflare.com ([176.221.114.230]) by smtp.gmail.com with ESMTPSA id h26sm2302857lfc.69.2019.10.29.01.56.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Oct 2019 01:56:29 -0700 (PDT) References: <20191022113730.29303-1-jakub@cloudflare.com> <20191028055247.bh5bctgxfvmr3zjh@kafai-mbp.dhcp.thefacebook.com> <875zk9oxo1.fsf@cloudflare.com> <5db73ba5afec7_54d42af0819565b855@john-XPS-13-9370.notmuch> User-agent: mu4e 1.1.0; emacs 26.1 From: Jakub Sitnicki To: John Fastabend Cc: Martin Lau , "bpf\@vger.kernel.org" , "netdev\@vger.kernel.org" , "kernel-team\@cloudflare.com" Subject: Re: [RFC bpf-next 0/5] Extend SOCKMAP to store listening sockets In-reply-to: <5db73ba5afec7_54d42af0819565b855@john-XPS-13-9370.notmuch> Date: Tue, 29 Oct 2019 09:56:28 +0100 Message-ID: <8736fcorpf.fsf@cloudflare.com> MIME-Version: 1.0 Content-Type: text/plain Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Mon, Oct 28, 2019 at 08:04 PM CET, John Fastabend wrote: > Jakub Sitnicki wrote: >> I was planning to split work as follows: >> >> 1. SOCKMAP support for listening sockets (this series) >> 2. programmable socket lookup for TCP (cut-down version of [4]) >> 3. SOCKMAP support for UDP (work not started) >> 4. programmable socket lookup for UDP (rest of [4]) >> >> I'm open to suggestions on how to organize it. > > Looks good to me. I've had UDP support on my todo list for awhile now > but it hasn't got to the top yet so glad to see this. > > Also perhaps not necessary for your work but I have some patches on my > stack I'll try to get out soon to get ktls + receive hooks working. Thanks for the heads-up. If you have a dev branch somewhere, I'm curious to see what's cooking. Otherwise I'll keep an eye out for your patches.