From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 2FA1BFE5 for ; Tue, 1 Dec 2015 16:19:46 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP; 01 Dec 2015 07:19:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,369,1444719600"; d="scan'208";a="5537382" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.107]) by fmsmga004.fm.intel.com with SMTP; 01 Dec 2015 07:19:43 -0800 Received: by (sSMTP sendmail emulation); Tue, 01 Dec 2015 15:19:41 +0025 Date: Tue, 1 Dec 2015 15:19:41 +0000 From: Bruce Richardson To: Panu Matilainen Message-ID: <20151201151941.GA33120@bricha3-MOBL3> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> <20151130171655.70e4ce25@xeon-e3> <20151201100333.GA32252@bricha3-MOBL3> <565DAE6E.5040102@redhat.com> <565DB356.9060602@6wind.com> <565DB580.9090209@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <565DB580.9090209@redhat.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] 2.3 Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2015 15:19:46 -0000 On Tue, Dec 01, 2015 at 04:58:08PM +0200, Panu Matilainen wrote: > On 12/01/2015 04:48 PM, Vincent JARDIN wrote: > >On 01/12/2015 15:27, Panu Matilainen wrote: > >>The problem with that (unless I'm missing something here) is that KNI > >>requires using out-of-tree kernel modules which makes it pretty much a > >>non-option for distros. > > > >It works fine with some distros. I do not think it should be an argument. > > Its not a question of *working*, its that out-of-tree kernel modules are > considered unsupportable by the kernel people. So relying on KNI would make > the otherwise important and desireable tcpdump feature non-existent on at > least Fedora and RHEL where such modules are practically outright banned by > distro policies. > > - Panu - Yes, KNI is a bit of a problem right now in that way. How about a solution which is just based around the idea of setting up a generic port mirroring callback? Hopefully in the future we can get KNI exposed as a PMD, and we already have a ring PMD, and could possibly do a generic file/fifo PMD. Between the 3, we could then have multiple options for intercepting traffic going in/out of an app. The callback would just have to copy the traffic to the selected interface before returning it to the app as normal? /Bruce