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 18096A050A; Wed, 4 May 2022 08:34:29 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BB9A24069F; Wed, 4 May 2022 08:34:28 +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 A8CEA40694 for ; Wed, 4 May 2022 08:34:27 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1651646067; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fie90TgniRxMW4Fgw3Knla+ZFuceoBzFrmlsjLA5UsE=; b=imqHNa6wsrThQSBicGToefeSaWL4oXrKDWFO3DBEVsRjRiIdb3EkkjpSMxznF1kaD07H0R Y30HmPLOqSh8pUxx2TGNiiMEctj+SXyiU25APkOax75PrV4eecQb4eUQATI2DwnuE5uQ5t WWp+v4fdroAi0aA9Io0jzs6uUxSXjHM= Received: from mail-lf1-f72.google.com (mail-lf1-f72.google.com [209.85.167.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-542-TmEp2VghNh-H8qC4ADe_-w-1; Wed, 04 May 2022 02:34:26 -0400 X-MC-Unique: TmEp2VghNh-H8qC4ADe_-w-1 Received: by mail-lf1-f72.google.com with SMTP id bq15-20020a056512150f00b00473a2e132a5so239984lfb.10 for ; Tue, 03 May 2022 23:34:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=fie90TgniRxMW4Fgw3Knla+ZFuceoBzFrmlsjLA5UsE=; b=70yA/vTcVtWHxe2AyX80MIheU5PJJONoGVZgjM91hmd/fNxs8J7tcjBoTWX8cD+xHQ upBsOXKqC3ZfI1pgyfyWf3QXoXCLisO1sB2Gn4FHwNCBFAlZpUakR5fjAJtyltmsZHpI 0kHVirK2AUu2KI1G2evsmN95ZalANVZukt40HJepZdZL6vSp9yX0PJQFmP7H4ka79GjX 0Do+zRKaqvAGnGZM/rZV7TKnpSnxIHrPpwsOUaDPToQrWtr58Z1QdE6pYfEJKuPH88GU SWbvS6UrJQOYZ6fmFLVHW5xAWSKA87JHL2m6/rR+OvbPVXaO4jHjHsdDfhJC7kkSxSJM 8WXA== X-Gm-Message-State: AOAM5337vIEEgmE1pOUV8+UBZzjE83gXxFSQlEotx+kS+OhlgchH3XmY 4Kgs8BoMtSz1iFZDEPXQLyT0vZ1GuJDMtSSYHlYNJwMVXpFawZ8k4DMewaGRr8uG7CUyidJYnmN GUpj6iQ0byd+zoGVh39g= X-Received: by 2002:a05:651c:1781:b0:247:daa7:4358 with SMTP id bn1-20020a05651c178100b00247daa74358mr11574299ljb.477.1651646064466; Tue, 03 May 2022 23:34:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzwY91XkbVLYU/7Atnpk4pFFg6DiP4XBVgXhScoQzXsOYeaWqUY7au6U7fwpwDv86RpcYxdj4YyOYItlXb8NlA= X-Received: by 2002:a05:651c:1781:b0:247:daa7:4358 with SMTP id bn1-20020a05651c178100b00247daa74358mr11574293ljb.477.1651646064279; Tue, 03 May 2022 23:34:24 -0700 (PDT) MIME-Version: 1.0 References: <20f0c2fc-b8bb-69c4-8e0a-9b2632893a4a@e-gaulue.com> In-Reply-To: <20f0c2fc-b8bb-69c4-8e0a-9b2632893a4a@e-gaulue.com> From: David Marchand Date: Wed, 4 May 2022 08:34:13 +0200 Message-ID: Subject: Re: Difference between i40e and i40en? To: =?UTF-8?Q?Edouard_Gaulu=C3=A9?= Cc: dev , Beilei Xing , Jeff Guo , Qi Zhang Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hello =C3=89douard, On Tue, May 3, 2022 at 9:05 PM Edouard Gaulu=C3=A9 wr= ote: > > I just received a brand new server with an Intel X710 T4L inside. I > hoped I could use it at 5GBaseT speed as claimed by Intel, but I couldn't= . > > In fact, I run ESXi 6.7U3 on this new server and it looks it doesn't > support this speed (2.5G neither). I downloaded Intel driver source code > and discovered there was an incompatibility between 5GBaseT and DCB. But > then vmware support team, point me the driver used by ESXi is i40en and > not i40e. > > Are those drivers totally different? It looks to. Error strings found in > vmkernel.log couldn't be found in the source code. Is there any way to > get sources for i40en? For patching and rebuild. > > Any idea on who I should write to discuss with those i40en driver > maintainers? Here or totally out of scope? DPDK provides userspace drivers for various nics. If you are looking at kernel drivers issues, then yes, your mail seems out of scope :-). Afaics, i40en is a VMware thing, so the solution is probably to continue with VMware support. I copied some Intel *DPDK* driver maintainers who might have a better idea. --=20 David Marchand