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 D330543B35; Wed, 14 Feb 2024 16:20:00 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5A4184026A; Wed, 14 Feb 2024 16:20:00 +0100 (CET) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com [209.85.208.41]) by mails.dpdk.org (Postfix) with ESMTP id 40B4840263 for ; Wed, 14 Feb 2024 16:19:59 +0100 (CET) Received: by mail-ed1-f41.google.com with SMTP id 4fb4d7f45d1cf-5639b00a25cso40863a12.0 for ; Wed, 14 Feb 2024 07:19:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707923999; x=1708528799; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=+HegJ7i7/Ix/4zGmINBYiLyYN+lR/SXVYi0vYSvK2Zk=; b=diCBcWcJXW3mdV5JAVzKIO6U8oo6XI3uCbNC7eCqlY/TZuiJGeOS8UlAY14CLfkj9u uk9TMhpBxX2QkdkUIMPooBqvEzrhP8mithVRjwc6nouZ2srTR2BXp0aTFiVSRy5gYTDG IZrz65WpzkxktSJ/7FNhvhBGi1tpiznUxoncKNHBt4N/Obqr8G326MHaA0J/CgR6NijQ pKlPxBGS4xGsNenXRljRuiNDWevGQYql9aH7UlN/3BFsmr5swMYFkrvcHWFe+kCM5Kyi mkPDprawLnmP43KgEhV7WBcsmAN0u7xNi3RoptnqwsVt5w9gDEoRGjPNBO8nXO74qV6b 2sUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707923999; x=1708528799; 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=+HegJ7i7/Ix/4zGmINBYiLyYN+lR/SXVYi0vYSvK2Zk=; b=HuiZyDIjnZKQ+8zwkYcyZrNRzzKmSb4JQZcLYc/B4T5PHCElGJxa8m8iC1U+9rg40t 2majqt75/N5uBuNWTcPstsrF48aqkqyh0mY/ua8IbcFe3dHogYnikVPPYe/uHGDZEfGP L89lfCikTJsAl4rlS3QBr9u/j6YocGruKqF/OauxKkXEKHcj3vf05C0r54Aag5Z0r1LN D02mCAOciim3HN9+17zwn2VZVvj0BoMzBctDsWOJXz5mdw0i1/GZeCrH/NNu5Oxu3Ffx F5eZC1EKpG2AsEqEfeEH3s5wuVJm4lhJTEKudEiiCWRienY40CrBwixZNoEFvw7WZj6e I3gg== X-Forwarded-Encrypted: i=1; AJvYcCUzvjMXK5QDyzsLZaLSj6FUZzxVc3N5Mi+2Tinavhn8Ip8yt0aRmPf9dt/XLhlSEHUaRbHDU8Y4n1O3Uxg= X-Gm-Message-State: AOJu0Yx2Ss0o9XQiwoB8GB2ESSIvjVs2wZc0FTa442mfSIIlZJ5JyG6F 87OYxVFBb2hh36SqdG7deHw1ZWqIjfcJqFuLndIVgOt0tmE//BS8xWqQhf0N4j6qgETmSST/dHj A5QwlyDSsfgPLh/x/9R1gKcmKnbo= X-Google-Smtp-Source: AGHT+IHVxrUXRcpLcFQQVkeHvGaWpBYWXRTtkm6r2nASv6se0jyU5O3Bl/rCKVS7a02KQRVkyhyMC2qZsU7iNavllBE= X-Received: by 2002:aa7:cc0f:0:b0:561:ef01:3fa3 with SMTP id q15-20020aa7cc0f000000b00561ef013fa3mr2413275edt.39.1707923998610; Wed, 14 Feb 2024 07:19:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Prashant Upadhyaya Date: Wed, 14 Feb 2024 20:49:47 +0530 Message-ID: Subject: Re: PMD for non PCI device To: Jerin Jacob Cc: Bruce Richardson , dev@dpdk.org 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 Tue, 6 Feb 2024 at 21:28, Jerin Jacob wrote: > > On Tue, Feb 6, 2024 at 9:20=E2=80=AFPM Prashant Upadhyaya > wrote: > > > > On Tue, 6 Feb 2024 at 19:43, Bruce Richardson > > wrote: > > > > > > On Tue, Feb 06, 2024 at 07:36:16PM +0530, Prashant Upadhyaya wrote: > > > > Hi, > > > > > > > > I have a usecase where I have to evaluate writing a DPDK PMD for a = non > > > > PCI/e device doing the ethernet packet i/o. > > > > > > > > Wanted to know if the above usecase is supported by DPDK infra and = any > > > > pointers on how one should go about writing a PMD for such a usecas= e > > > > if supported. Would appreciate any inputs. > > > > > > > Hi, > > > > > > yes, such a usecase is supported, but the specifics of how to go abou= t it > > > will vary depending on the type of PMD it is. DPDK already supports a= range > > > of other types of PMD, for emulated, or SW backed PMDs, e.g. net/pcap > > > driver, and drivers for various SoCs which don't use PCI. For the cas= e > > > where the PMD is backed by real hardware (or an emulated device that > > > appears to a VM as a piece of hardware), you may want to consider wri= ting a > > > "bus" driver for DPDK to support probing of the device. For non-HW > > > devices, the "vdev" bus may be what you want to use, where probing is= not > > > done and devices are created in response to cmdline arguments on init= , or > > > via C APIs later in the app. > > > > > > Regards, > > > /Bruce > > > > Thanks Bruce, this is helpful. Is there any PMD in DPDK code that you > > can refer me to for any SoC which does not use PCI (the usecase of > > backing by real hardware), that would be great to follow. > > > See drivers/bus/* > > Based on your description, vfio-platorm will be the closest > match(driver/bus/platform) > > > > > > Regards > > -Prashant Thanks Jerin, this is helpful. One more question -- would you or anyone else on the list have information about any off the shelf/custom board with ARM cores (preferably 64 bit) which does ethernet i/o with a non PCI device on that board and for which a DPDK PMD is already available ? I wanted to compare the perf difference on such a board with and without PMD and hopefully read the PMD code for that device as a reference if available. Regards -Prashant