From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5CA6EA0543; Tue, 25 Oct 2022 10:23:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 34A1340A89; Tue, 25 Oct 2022 10:23:23 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 18EFF400D5 for ; Tue, 25 Oct 2022 10:23:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666686201; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ul3aP33gEoRC1aOKdwFA1ScvtCNEMrVKdICRa+RBQo0=; b=D1JFd8B95P0Qg80zoGnJ7f1dvL14HPJwu/iTAjy41GZz2etiHPXa5IG/3tH0fdKm3WGZrp sDhFUb7IHSSAoPsTxnW+UyIRhSghxfGlweX/UPaTfwpFnn65XadM834ClM+XX/0Pm4LPPj HT/86AyFxIodY0NW2QHoM6IJB7QFjEc= Received: from mail-pj1-f70.google.com (mail-pj1-f70.google.com [209.85.216.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-112-SsDPUYxWPVWzctRvV6a6Hw-1; Tue, 25 Oct 2022 04:23:20 -0400 X-MC-Unique: SsDPUYxWPVWzctRvV6a6Hw-1 Received: by mail-pj1-f70.google.com with SMTP id ls4-20020a17090b350400b0020d63c0efb9so10334746pjb.0 for ; Tue, 25 Oct 2022 01:23:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ul3aP33gEoRC1aOKdwFA1ScvtCNEMrVKdICRa+RBQo0=; b=XTPXmM3CLAsL1es/4X9B777pZ1Y+UPAQdivJVnNMKj2v6s3V+PkSHk3P3N76QlZB3N 0+0drxElCnYb7bDOolXs4nTTJLalw+pVJG3Xb9Ws4zi/MyTAxgVax913CPplgI3sTxMs hP3QmNwi7N8Wv1coO69z1fks0OWLVRXzktPurFs9oHmlfzhqww9vPkOjXbcHfeeZpQPd S2JXmIScwRFYPGzp11g8ZJiYcW+JSZzpQC7glTpAvw+9WeHbGdnD3v9GvoHpyHw3WDFk 3DppCcFGBkjspLDvSWSPmvtj+DlKgKfi6yc62zkuIR4OiWg4ovqvCjk8YSm/hoVbIqyq Zk4A== X-Gm-Message-State: ACrzQf2Lt50wayuhpDbIef4TBPCTE1DBzJlNeR7qtM/cHYbOiOI8FBg9 cBKwygDc8OiQs3J5nwCXJWmX4f7PsekafmYjndqO+7giEQIsfCayK4JVfirxZ6F7WOx1U0BJvrt fB4ghBQsne8hQgvmWb00= X-Received: by 2002:a17:90a:428e:b0:205:d5fe:e0b3 with SMTP id p14-20020a17090a428e00b00205d5fee0b3mr42801088pjg.33.1666686199213; Tue, 25 Oct 2022 01:23:19 -0700 (PDT) X-Google-Smtp-Source: AMsMyM46peaV2fjs7oJCmUksxyHdUG1Dxi59imjujMRKyraVtkztxw1+55eTFykizjXzOyo2LxNX+NhyJC0SWJl/I2c= X-Received: by 2002:a17:90a:428e:b0:205:d5fe:e0b3 with SMTP id p14-20020a17090a428e00b00205d5fee0b3mr42801067pjg.33.1666686198939; Tue, 25 Oct 2022 01:23:18 -0700 (PDT) MIME-Version: 1.0 References: <20221014071209.1501977-1-yux.jiang@intel.com> In-Reply-To: From: David Marchand Date: Tue, 25 Oct 2022 10:23:07 +0200 Message-ID: Subject: Re: [PATCH V2] doc: add ice in-tree driver version for Intel NICs To: "Peng, Yuan" Cc: "Jiang, YuX" , "dev@dpdk.org" , "Zhang, Qi Z" , Maxime Coquelin , "Mcnamara, John" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, Oct 25, 2022 at 4:52 AM Peng, Yuan wrote: > > Hi Marchand, > > Tested platform in this document lists all the platforms including CPU, OS and NIC type with SW package version. > We submitted the patch to add our actual tested ice in-tree driver version of E810 NIC in this DPDK release. > I think it should be added here. Ok, you can put the information here, as it was before. But I am asking for more, see below. > doc/guides/nics/ice.rst is a document for ICE driver introduction. - Sorry, I meant iavf.rst. The dependency on ice PF driver wrt features availability of the iavf driver must be documented. We had reports for couple of issues. Those issues were hard to understand due to really poor (read: absent) documentation. After investigating (having to play with differents versions of kernel, dpdk, firmwares, oot driver ...), we realise it is due to poor decisions from Intel on implementing features in the ice OOT driver only. Because of this, DPDK developers are locked with this OOT driver instead of relying on the upstream kernel. This is a bad thing for both DPDK and kernel communities. - This current patch only shows focus for tests against two distributions, with a fixed release version. I insist that Intel QE must validate the iavf dpdk drivers against the *upstream* ice kernel driver. -- David Marchand