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.1 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 9EE0CC43381 for ; Thu, 14 Feb 2019 00:46:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6506F21904 for ; Thu, 14 Feb 2019 00:46:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="H/hbU2JR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727061AbfBNAqb (ORCPT ); Wed, 13 Feb 2019 19:46:31 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:32825 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726165AbfBNAqa (ORCPT ); Wed, 13 Feb 2019 19:46:30 -0500 Received: by mail-pf1-f195.google.com with SMTP id c123so2093562pfb.0 for ; Wed, 13 Feb 2019 16:46:30 -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=7yyQJ6CgqUyyV5mJ0Jme9tXZl+6uS7Zxq+xLKD1mgpg=; b=H/hbU2JRyMlfOGPiPt94Yt7bBbqYMTFtJjJ1VxVZgYF/bHUBAqF6CK2DSCHeVSQEtW NbHEFokK8Vzub8dpLRKAx9NQ6pCs7Z3r+nHJz93smwINve3Rc9zUWvccK/zdC7zv4Pl8 HkD5apAq2WcNORNQZ6A4cxdPwTu21UcCKgi3LVoILbdQSbMWeJbgJpfypR69nd7YYrKB 3Ln7A9JWP2B8HydxstAoRwhCiq67h8cIIDbaWM29/P0lb8+QlEydJc+ao7NrFFEtVAov 5OisquHoO56mZmp9q4+ypwTNbdrlYkOb6VDjcGpMGeRGz7li3FUmp0bbKjm25m4/qd1c cjAg== 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=7yyQJ6CgqUyyV5mJ0Jme9tXZl+6uS7Zxq+xLKD1mgpg=; b=p6vQdC6livmw0E9Y79NH/S0UlJBKv1wsunRM6YeCMzDtfqmQZ+2N5r6jdENXDc4U+m 8Lqbf6TENE/DDdyWScNqcSMHFqC3xv5AVRBVYRLUuSttiK5wR3az4d3RjoRlCa/ZPYxK tnJw4pMqJCJRpwfzwCQYiEaWC3fVAp+ryQuEU978t1mabah+4WZeSaauUyawkgnKl9uH /Dbhj1r9MuwEFIyUv+vdDASh5xzq4Lo3vRNIjx65JerADQK1sbsaRKWrR1MaSQYz4V0u /plpbdYTJdKnR19ZV1XFDmmSW8QBVtHbWg+R9nJWuw+t7YhRsy3+mUEiyAAoVjc6DPwJ xSZg== X-Gm-Message-State: AHQUAuYXpseW8Kk3bYph0cjrayfPdAb3vD/LBaaNZaGjjb/U4H+eX7FV X8B7iVkVa4ZZDYf22jxaUGHXavF7 X-Google-Smtp-Source: AHgI3IbqfireCe3DtDF/PkwrxckE0K4ZLPZeXLtPow423cBJkx+IsJ3ps2UWKfukHzFuHbjciSos1A== X-Received: by 2002:a63:1204:: with SMTP id h4mr1005580pgl.51.1550105190020; Wed, 13 Feb 2019 16:46:30 -0800 (PST) Received: from ?IPv6:2601:282:800:fd80:1d6b:31d6:ccdb:d65a? ([2601:282:800:fd80:1d6b:31d6:ccdb:d65a]) by smtp.googlemail.com with ESMTPSA id e63sm787942pfc.47.2019.02.13.16.46.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 16:46:28 -0800 (PST) Subject: Re: [PATCH bpf-next v11 0/7] 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 , Willem de Bruijn References: <20190213195341.184969-1-posk@google.com> From: David Ahern Message-ID: <783b5578-cba4-904d-4ade-c8c08b47a3ba@gmail.com> Date: Wed, 13 Feb 2019 17:46:26 -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: <20190213195341.184969-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 2/13/19 12:53 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