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 31F45C2D0DB for ; Mon, 27 Jan 2020 13:05:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 042AA214D8 for ; Mon, 27 Jan 2020 13:05:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=cloudflare.com header.i=@cloudflare.com header.b="OdqOcuO1" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726029AbgA0NFH (ORCPT ); Mon, 27 Jan 2020 08:05:07 -0500 Received: from mail-lf1-f68.google.com ([209.85.167.68]:36191 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725807AbgA0NFH (ORCPT ); Mon, 27 Jan 2020 08:05:07 -0500 Received: by mail-lf1-f68.google.com with SMTP id f24so6140838lfh.3 for ; Mon, 27 Jan 2020 05:05:05 -0800 (PST) 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=cV3DBU5zIwSvjSC3uugvJ7qJ6byUG1P03d9feBBjhNY=; b=OdqOcuO1vfgcedmxIHCikjp7GzSAV6nfhvOpxZMhgSUwVZRKBeI3UBPbwb+Ocn32pV Z2GoqgMggaiij2aYR47x3OhMaAjigJY8sBsCVZFsfQLq8iGESdkouzCu9jrZ47wDSZST Alzv3GbsSQ/qwS4ukoIfciieFuq1AmoMpjXpc= 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=cV3DBU5zIwSvjSC3uugvJ7qJ6byUG1P03d9feBBjhNY=; b=DvmAQ523ysdYcgy4g4CwBOOrpm5X4Yb2XpU7freeNpofSO3qHY0VVxedVl3P5tUlud nGzbHOcb572H3JD8Wfjs4UKW5fPKSy0mBWyX0qB1DsOzLV8l3m/kGmMdxMURU4cOhOSg xVUVoIOT6Y9pm0UporUCkIqMD/rEg9symbDiA59Yz44LIbrLiLo0g4RJvs7eA5bIWnq5 eUbUZhosAj9RMJCI6qK9Tkp7Kw4FiBd2x6JscHitBLIqoj6QP3d1s77lNBIukOf140dR luXfOrDK8cR3GjJGp7pLSTOHimHoZo/5iV7xQFCpdByWFLqL9qyYAMst4C3A3wzUCzmG zO2A== X-Gm-Message-State: APjAAAWfMercrs0f4qMENxCfw6pcg4LqrP4JNZ5IgGaMNhbb0sQxVDE+ qDso6YA18NCsca9QWVYq1l2MJA== X-Google-Smtp-Source: APXvYqyywebOR6ItZ4HzCAQ7awqLbCj9qnIelmZjLSX349f6NxC1ODKbnmZtbqdDMzmidNrY9yE3wQ== X-Received: by 2002:a19:4855:: with SMTP id v82mr7742497lfa.197.1580130305156; Mon, 27 Jan 2020 05:05:05 -0800 (PST) Received: from cloudflare.com ([2a02:a310:c262:aa00:b35e:8938:2c2a:ba8b]) by smtp.gmail.com with ESMTPSA id x29sm10085250lfg.45.2020.01.27.05.05.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Jan 2020 05:05:04 -0800 (PST) References: <20200127125534.137492-1-jakub@cloudflare.com> User-agent: mu4e 1.1.0; emacs 26.3 From: Jakub Sitnicki To: bpf@vger.kernel.org, Daniel Borkmann Cc: netdev@vger.kernel.org, kernel-team@cloudflare.com Subject: Re: [PATCH bpf-next v5 00/12] Extend SOCKMAP to store listening sockets In-reply-to: <20200127125534.137492-1-jakub@cloudflare.com> Date: Mon, 27 Jan 2020 14:05:03 +0100 Message-ID: <87blqpcao0.fsf@cloudflare.com> MIME-Version: 1.0 Content-Type: text/plain Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Jan 27, 2020 at 01:55 PM CET, Jakub Sitnicki wrote: > Make SOCKMAP a generic collection for listening as well as established > sockets. This lets us use SOCKMAP BPF maps with reuseport BPF programs. > > The biggest advantage of SOCKMAP over REUSEPORT_SOCKARRAY is that the > former allows the socket can be in more than one map at the same time. > However, until SOCKMAP gets extended to work with UDP, it is not a drop in > replacement for REUSEPORT_SOCKARRAY. > > Having a BPF map type that can hold listening sockets, and can gracefully > co-exist with reuseport BPF is important if, in the future, we want to have > BPF programs that run at socket lookup time [0]. Cover letter for v1 of > this series tells the full background story of how we got here [1]. > > v5 is a rebase onto recent bpf-next. Patches 1 & 2 has conflicts. I carried > over the Acks. Well, this is embarassing. Please don't apply. I have some uncomitted local changes. Will roll v6.