From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCH net-next v2 3/4] net: check tunnel option type in tunnel flags Date: Thu, 28 Jun 2018 19:01:52 +0200 Message-ID: <20180628190152.539bfc67@redhat.com> References: <20180627043937.25431-1-jakub.kicinski@netronome.com> <20180627043937.25431-4-jakub.kicinski@netronome.com> <20180628094206.62b6d8e2@redhat.com> <20180628095452.6f23fdf4@cakuba.netronome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Daniel Borkmann , davem@davemloft.net, Roopa Prabhu , jiri@resnulli.us, jhs@mojatatu.com, xiyou.wangcong@gmail.com, oss-drivers@netronome.com, netdev@vger.kernel.org, Pieter Jansen van Vuuren To: Jakub Kicinski Return-path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:60944 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933945AbeF1RCA (ORCPT ); Thu, 28 Jun 2018 13:02:00 -0400 In-Reply-To: <20180628095452.6f23fdf4@cakuba.netronome.com> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 28 Jun 2018 09:54:52 -0700, Jakub Kicinski wrote: > Hmm... in practice we could steal top bits of the size parameter for > some flags, since it seems to be limited to values < 256 today? Is it > worth it? > > It would look something along the lines of: Something like that, yes. I'll leave to Daniel to review how much sense it makes from the BPF side. Thanks! Jiri