From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by dpdk.org (Postfix) with ESMTP id 6DBB65927 for ; Thu, 27 Aug 2015 02:15:05 +0200 (CEST) Received: by pabzx8 with SMTP id zx8so4198676pab.1 for ; Wed, 26 Aug 2015 17:15:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-transfer-encoding; bh=Wunrz0GBtiBSmRs0jJbtflGAiPPoGG6Yj8M9V3cAJiM=; b=MkaspAYHKRPrePewka4eRM8piN/tvYn4Zf+8BbXg2BNV9iBi9FeWdakzg9lA19gZHh KKVU7XwUtqwHTjDigpoI7RHuTFDZwvWNdNwDkcq1aVV1uaicU3Wk3zaYfxwZHjKpZp10 N2vCWnf2kyPcT0uVLf6SkFjqsyyCPnaNqYJyXUc98zZW5uFgA4oeiT0NtsUh5qAim2V6 F8MHe4dV44DcXnl5K0mBU52gExViHiUzL+QF9L19QK0/fT3NXBKy//kUj52ZRPcPaih3 JiOXGAIqtk3YplUGzGqVy9oN/MpSK+KuYf2GnkV2TolZAZMgrtku2Cu8JTuF+Gn7s6Xg r3Tw== X-Gm-Message-State: ALoCoQmudWHs372AIAj8SSzJ1drW30LyxwbYoqlayo4WC0he48cfhEuXPBFyPesOj/tqalJ8tB7U X-Received: by 10.66.63.69 with SMTP id e5mr2099573pas.156.1440634504601; Wed, 26 Aug 2015 17:15:04 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id yt9sm226739pac.32.2015.08.26.17.15.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Aug 2015 17:15:04 -0700 (PDT) Date: Wed, 26 Aug 2015 17:15:16 -0700 From: Stephen Hemminger To: dev@dpdk.org, Helin Zhang Message-ID: <20150826171516.7160bcb2@urahara> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] BUG - KNI broken in 4.2 kernel 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: Thu, 27 Aug 2015 00:15:06 -0000 The network device ops handles changed again. Does KNI really need to keep yet another copy of the Intel driver code. There already are 4 versions: 1. Out-of tree base driver 2. In-kernel mainline Linux driver 3. DPDK driver 4. KNI DPDK driver No wonder they can't stay in sync.