From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 02/13] sk_buff: add skb extension infrastructure Date: Wed, 12 Dec 2018 16:38:32 -0800 (PST) Message-ID: <20181212.163832.2133855211032994962.davem@davemloft.net> References: <20181210145006.19098-1-fw@strlen.de> <20181210145006.19098-3-fw@strlen.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: fw@strlen.de, netdev@vger.kernel.org To: ssuryaextr@gmail.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:42242 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726278AbeLMAid (ORCPT ); Wed, 12 Dec 2018 19:38:33 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Stephen Suryaputra Date: Wed, 12 Dec 2018 13:16:57 -0500 > On Mon, Dec 10, 2018 at 11:20 AM Florian Westphal wrote: > >> +#ifdef CONFIG_SKB_EXTENSIONS >> +enum skb_ext_id { >> +#if IS_ENABLED(CONFIG_BRIDGE_NETFILTER) >> + SKB_EXT_BRIDGE_NF, >> +#endif >> + SKB_EXT_NUM, /* must be last */ >> +}; > > How about when proprietary extensions is desired? There are cases > where our system has to pass special metadata from input to output in > skbs. Proprietary extensions will absolutely not be taken into consideration when designing upstream features in the Linux kernel.