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=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham 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 C0E39C169C4 for ; Thu, 31 Jan 2019 16:38:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8DF6B20820 for ; Thu, 31 Jan 2019 16:38:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="vcK/CzxN" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388588AbfAaQiV (ORCPT ); Thu, 31 Jan 2019 11:38:21 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:45375 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388493AbfAaQiV (ORCPT ); Thu, 31 Jan 2019 11:38:21 -0500 Received: by mail-pf1-f195.google.com with SMTP id g62so1694550pfd.12 for ; Thu, 31 Jan 2019 08:38:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=3ZITCkGKOdMUN/7R/0e5gr3S01vL60Y0CzTd7eyFH+U=; b=vcK/CzxNY0SrYLvSc5Mfx4DIWw1C1UpW2QTh5CJLeMnBT3dBZ61q6J2ko1ew7kmPHK 6auBtAQCdFRjDq4IBAsnIvx9zfB4mhWaFORmX/coHWKZDXVMuTj3EqCyiJXWd9lYpBXj 7U6XoZPBXOlKupK6mJaG/to+VoGdIXYBv4CgbFc3kudHjGOu/WSvIQS9GbXLRAhfNu6Y Su87Qf2IoxJr9ctOakZoGDIuXqVw/tuXDRJ2i1gJkyJHIc/SgcffrtE5MTcjxruDjW7x aW8twJx5ITls/nz2FyqCjBq9xrn6tvec3f11tUSizVp3UwBd76FtP5fBjor/dMdcyvpH HkjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=3ZITCkGKOdMUN/7R/0e5gr3S01vL60Y0CzTd7eyFH+U=; b=lhaNgBF4Dxckie8e5Dj2Jpe67Dsu5AQMP17yLSOVXySJabVClhVuqG54ncI5V5EEH8 YaG9MyR34vPvbAXFDTFSz0xvgGM/nbW6N4FDCAf0l1yu+vLQLnqd3NAe44fRO+bJY+PD gY9o5Z9ATbkYDFwF6DGlPZ1dfie9lu/l7Pm7CFupCj9j5zEIvxZa957R2/TxvLRGdtAQ 7y6VCOfTva7/QdSMnwICENoATApbMJVB5Y6VwTvvp0HQfBgPpT14jARJzH9hPM5qjwOq 3VeQc8KoxmsXov/Vxa4aRhmvsohQlovRxoa98obQFCPFAv9O4d0iKdEaIpKO4nF6KL0w QVJg== X-Gm-Message-State: AJcUukcfPms9FM9UuZqaN0dmyrqJNEUO12LUukcBXZ05ob5K/YZQTwpS V911AfR/RSgID32ZWbdNxlI= X-Google-Smtp-Source: ALg8bN4stpbdLQzmSNUUz6ifKzp2Hplu2cEjeI2iJIhu73QTrmd3LbEqj2eyFVoYEnDcnD1TYDavhA== X-Received: by 2002:a63:c0f:: with SMTP id b15mr32406157pgl.314.1548952700411; Thu, 31 Jan 2019 08:38:20 -0800 (PST) Received: from ?IPv6:2601:282:800:fd80:c815:f466:5ce2:c2e2? ([2601:282:800:fd80:c815:f466:5ce2:c2e2]) by smtp.googlemail.com with ESMTPSA id z7sm7475953pga.6.2019.01.31.08.38.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Jan 2019 08:38:19 -0800 (PST) Subject: Re: [PATCH bpf-next v5 0/5] bpf: add BPF_LWT_ENCAP_IP option to bpf_lwt_push_encap To: Peter Oskolkov , Alexei Starovoitov , Daniel Borkmann , netdev@vger.kernel.org Cc: Peter Oskolkov References: <20190130235136.136527-1-posk@google.com> From: David Ahern Message-ID: <9a407aa4-0f2a-0770-108d-549602bbdb73@gmail.com> Date: Thu, 31 Jan 2019 09:38:18 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20190130235136.136527-1-posk@google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 1/30/19 4:51 PM, Peter Oskolkov wrote: > This patchset implements BPF_LWT_ENCAP_IP mode in bpf_lwt_push_encap > BPF helper. It enables BPF programs (specifically, BPF_PROG_TYPE_LWT_IN > and BPF_PROG_TYPE_LWT_XMIT prog types) to add IP encapsulation headers > to packets (e.g. IP/GRE, GUE, IPIP). > > This is useful when thousands of different short-lived flows should be > encapped, each with different and dynamically determined destination. > Although lwtunnels can be used in some of these scenarios, the ability > to dynamically generate encap headers adds more flexibility, e.g. > when routing depends on the state of the host (reflected in global bpf > maps). > For the set: Reviewed-by: David Ahern