From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: [PATCH bpf-next 1/2] bpf: add BPF_LWT_ENCAP_IP option to bpf_lwt_push_encap Date: Fri, 30 Nov 2018 16:51:58 -0700 Message-ID: <49ceae53-3f87-44e4-eb8e-3f8bb5151a14@gmail.com> References: <20181129002248.241080-1-posk@google.com> <7c92e102-3e1f-04e3-5387-1616baaa6430@gmail.com> <50f3135e-5e24-d152-b99c-ca86260fbe12@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org, posk.devel@gmail.com To: Peter Oskolkov Return-path: Received: from mail-pl1-f193.google.com ([209.85.214.193]:42074 "EHLO mail-pl1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726013AbeLALDC (ORCPT ); Sat, 1 Dec 2018 06:03:02 -0500 Received: by mail-pl1-f193.google.com with SMTP id x21-v6so3535027pln.9 for ; Fri, 30 Nov 2018 15:52:01 -0800 (PST) In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 11/30/18 4:35 PM, Peter Oskolkov wrote: > Thanks, David! This is for egress only, so I'll add an appropriate > check. I'll also address your other comments/concerns in a v2 version > of this patchset. Why are you limiting this to egress only?