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 85F3F42546; Fri, 8 Sep 2023 11:15:18 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 29DCA402C5; Fri, 8 Sep 2023 11:15:18 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id E0CE540285 for ; Fri, 8 Sep 2023 11:15:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1694164516; 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=4V09m3TYBk+FnEgGc5hJzHLMu6pradP8I665T3JtN6U=; b=PWlGQacLh8yF99yFCw+Wil9n/NJBzE2LeEY7PMaJIih2FBN4/Ebx6fOZi6WaXolHN9x27l O9xEMPbI5OxABuJGpDbDDDfa9r0av+wV69Ai7CkwSEtJ/wZo5zYKzxsktjhZZYFAXqnVLZ RkzB4Y4K1uOL2/l8LBfMj3VapUcpKCk= Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-623-mFzJuKidOCanPTQ1WPgl2w-1; Fri, 08 Sep 2023 05:15:14 -0400 X-MC-Unique: mFzJuKidOCanPTQ1WPgl2w-1 Received: by mail-lf1-f71.google.com with SMTP id 2adb3069b0e04-4fe55c417fcso2054315e87.0 for ; Fri, 08 Sep 2023 02:15:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694164513; x=1694769313; h=content-transfer-encoding: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=4V09m3TYBk+FnEgGc5hJzHLMu6pradP8I665T3JtN6U=; b=pSZy/2b/cufSH7XqQ8VK4XLjm9j2alQMQkUPZzkluVjR/oSFyJ9yMJ4oF7XxG8xsgX VVQASt4xGVwK8f241FAagNVBdo9Yw6wLHk4LXhAZJZpQ3kZhZGl/WBrzHdNqeCBv/bUe Bi/Oc3IRFByzFMRyptXZxBIMjWRuSk1fyS/4SiGOxzwxwvsgJB2w9+uEjCApvMNqZnEb aEe0PNP9xpWPKgrDvKHXE7Wl/UD1JcgkT01DBVaeJ9MGPVlSThh9FmicaUTuUTlzJx9A RVtADTHs5hxh6FmSKDmWiDZWuBAo9PSG0ewplhkrAASx92Ce9qdy6BZaARan052spM/+ E8ag== X-Gm-Message-State: AOJu0YxWyrfptWI1krJdHj42uy8CzTYYq1GtwRLcxetOGpMaPwn5RSgT IiLlPXm+xcs8f/cCMZB893tUgXE+aZJBDaGsnqNPiCTkHJAEJgLK46q9/RBAfmVZvIcBJo7fkfC JyIvLxgKZPySBwH/HJLU= X-Received: by 2002:a05:6512:368b:b0:500:8fcb:e0c9 with SMTP id d11-20020a056512368b00b005008fcbe0c9mr1207354lfs.69.1694164513536; Fri, 08 Sep 2023 02:15:13 -0700 (PDT) X-Google-Smtp-Source: AGHT+IH+KxZlgw6RRHHmRT5+TDeMCkgbS9St3LYvtISAtP35s25oxmj7lKgDganG7V0gonAQg8gsCkMyshh+2PFv+As= X-Received: by 2002:a05:6512:368b:b0:500:8fcb:e0c9 with SMTP id d11-20020a056512368b00b005008fcbe0c9mr1207337lfs.69.1694164513158; Fri, 08 Sep 2023 02:15:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Fri, 8 Sep 2023 11:15:01 +0200 Message-ID: Subject: Re: Troubleshooting DPDK in Intel Ethernet NIC To: =?UTF-8?Q?Ant=C3=B3n_Rey_Villaverde?= , simei , Wenjun Wu Cc: dev@dpdk.org, Qi Zhang , "Mcnamara, John" , Qiming Yang 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 On Fri, Sep 8, 2023 at 11:05=E2=80=AFAM Ant=C3=B3n Rey Villaverde wrote: > > Afaics, this nic is not supported by DPDK drivers. > > Indeed there is nothing about "15fb" (the PCI ID of my NIC) in the output= of ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd , so I guess it is n= ot supported. > > On the other hand, I do see that the I219 family of my NIC (I219-LM) is p= resent in the list https://core.dpdk.org/supported/nics/intel/ under e1000e= category. > > Is this a contradiction or am I missing something? I reached the point where I can't help :-). Some I219 nics support has been added ealier this year (commit a33e1a5bcd3f ("net/e1000: support more I219 devices")). Maybe adding support for your nic is a simple matter, but passing the ball to Intel maintainers who are the right people to answer. --=20 David Marchand