From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49]) by dpdk.org (Postfix) with ESMTP id DD8E0282 for ; Thu, 15 Dec 2016 18:16:17 +0100 (CET) Received: by mail-pg0-f49.google.com with SMTP id x23so21994299pgx.1 for ; Thu, 15 Dec 2016 09:16:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=dADF8Yuitg3qswEg9Gm8hSYMqF03NikOH211MXo0mlU=; b=JR6gGKRayqK7VU1CFCSWL679qpew92BlixYXCsdYZM/HaeWNTN6jGFvFkp9b+mOfcX 8xo1pNpGk6kBo3wjYt6+77BSbljgB7SxAHqtJ2B7O1CiOK11Mp19P4Wo137lTE6B2QWS 9N7tpg6oPu8UVx/YZY2aH+zM+UEvo+nugq5RIKJTRopjClu5jAzqqseWIppJfs0qR8qX wfMw639xJ6eUyLloiwtOrAr7zATML3/2AjdyKh2mFxsmV7coPRCLvmSS5WUDilstwQbN P/+Cw/480Lr4UszrJSuDfLtuO/ZTWKOodbsA6LWs+a0wxXM9WKOo6xS4TFP8KxVdq5Pi oNQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=dADF8Yuitg3qswEg9Gm8hSYMqF03NikOH211MXo0mlU=; b=s+YONpDXHPaiOAiJRhKUTHyMM8oFm1vpSL2NeCSb9gf34geakPwwFCrzlGs4EL03vd NkvFW40gewWhw3uwCayEHPt08xm5zYkiD8IAwbhDUdkwPhpQBvYadGPtnqPqnjYMFQA5 kZCcV2yC9ldAyCO2LFdq52CigqXRuGGGlXCLKGYvT2/prUFYSsB5WOLhdMG0dJZ6+/T4 5nJm7rM/uuw+llw5VR8jTooA5OdG7cfBCUXpB5UmhQ8uFGJCHq/wSeAZQWHfc87XGVd1 TxcsNGOwfKMY2rgks0vlrJ52NJKnSjj7QeILUnP0+SkezSzAi/LMzJWRjATnyipjovvE YBKA== X-Gm-Message-State: AKaTC005amxv3418+3eldtxs7nr5H8AVGbBQTPteaiVYmrlMdxmECGroQjA6RIC3m8ELfA== X-Received: by 10.99.115.82 with SMTP id d18mr3836451pgn.56.1481822175551; Thu, 15 Dec 2016 09:16:15 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id 1sm5981841pgp.1.2016.12.15.09.16.15 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 15 Dec 2016 09:16:15 -0800 (PST) Date: Thu, 15 Dec 2016 09:16:08 -0800 From: Stephen Hemminger To: Ferruh Yigit Cc: dev@dpdk.org Message-ID: <20161215091608.25ab1b43@xeon-e3> In-Reply-To: <53ad7e36-380c-e5b7-a002-1690d2e63603@intel.com> References: <20161214154049.698de2e8@xeon-e3> <53ad7e36-380c-e5b7-a002-1690d2e63603@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] KNI Questions X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 17:16:18 -0000 On Thu, 15 Dec 2016 11:53:59 +0000 Ferruh Yigit wrote: > Hi Stephen, > > <...> > > > > > Which raises a couple of questions: > > 1. Why is DPDK still keeping KNI support for Intel specific ethtool functionality. > > This always breaks, is code bloat, and means a 3rd copy of base code (Linux, DPDK PMD, + KNI) > > I agree on you comments related to the ethtool functionality, > but right now that is a functionality that people may be using, I think > we should not remove it without providing an alternative to it. > > > > > 2. Why is KNI not upstream? > > If not acceptable due to security or supportablity then why does it still exist? > > I believe you are one of the most knowledgeable person in the mail list > on upstreaming, any support is welcome. It should be upstreamable but I doubt it would make it past the maintainer. Mostly because it supports DPDK which he is not in favor of but also since it is a specialized interface only usable by DPDK, ie. not a general infrastructure.