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 193CD43A9A; Tue, 6 Feb 2024 16:58:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 95338402B5; Tue, 6 Feb 2024 16:58:41 +0100 (CET) Received: from mail-oo1-f50.google.com (mail-oo1-f50.google.com [209.85.161.50]) by mails.dpdk.org (Postfix) with ESMTP id AFBD24026B for ; Tue, 6 Feb 2024 16:58:40 +0100 (CET) Received: by mail-oo1-f50.google.com with SMTP id 006d021491bc7-5961a2726aaso3339790eaf.0 for ; Tue, 06 Feb 2024 07:58:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707235120; x=1707839920; 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=JvLSjvOWvTf1+e6RmhXctRW2HBkPXScHNhk0vO68bfQ=; b=C7xsO2loPAk+jBofDWIVIIzex91VsA8lVAu/oPzAWOaYJWylqVTR0Qgi39J7lqGvLl kjxPtVSIDDreYLQjWe/4fZDk3misjMUGUlW+jC0TMT/gvVg2aMCcSuhyBT0oObUAzTS1 eF4fTHnVE7GVqxkap3H6GtQ8EecezAG1k6qw0vvOIXMsaMPsVULzgHRg4CXLTBxXnw4G Z1aXr59GYNgRViOV2rmEMZzP/p/sZIMHVNApsxwyiMqKbo6+L0XUW3YpW0RJQJT2fkwf fHcTexj8+z/G1sMobCpm6OGgELtTDtQ52ho2Wisr2/Ef+nU5ESUD1c3Ux00XlXNR1sCe SkJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707235120; x=1707839920; 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=JvLSjvOWvTf1+e6RmhXctRW2HBkPXScHNhk0vO68bfQ=; b=e+NHZIIqbN2Ki2EV5Gqe5UdFnDIV0cC8hTCmDmHryuE3NcEkbx55o5Yi186FWQl6gY YoWhO1PKUv69vVfbLgfyfUehgsoj7pf+T3ko8crr+RsGAS1Nr1RKWyvT3FwRASb7MnCv xv+jbRdW40foaB6BI7+YWquwILGxmMh7/KgIMfMFWRHXwHv6LFeTw8OJMcKdIEX1DLEy DPD/EfkH4q0+r1AfdyPoGNKaftQaxZI43QL5q+T8BDawqhNKuy3rXInn1metoIoiXxjF +2x6Q6JTz7kfrC1xjiFywGRZkG28lNYxvDy8w36fBr2DakgPtx/+Lt3Ww/C7ZqFV1t8P Yeog== X-Gm-Message-State: AOJu0Ywsc0jPzAVeT6KaZQ1GG7hsqukCRiiRac2LSVaE/e+j18SP3P53 rujQmG7hQBjkwP9tewzdEHYCJNccJg2QaQsRYLTes9zNBKy/MQ/+rtvL+asVu/rSPuyCWoCnQ6d davHVqo/PFlFKWaiH4X2qw0OVCkg= X-Google-Smtp-Source: AGHT+IFYiSoUjjSL/xscePSFR53/Fo5JkD1MmXdDX01ZT5EIWZxu9Gh6mXeXP9JHhJtT88pIdFJiWlEFjGxWR6Bd8Lo= X-Received: by 2002:a05:6358:d381:b0:176:9bfd:d092 with SMTP id mp1-20020a056358d38100b001769bfdd092mr2544510rwb.18.1707235119462; Tue, 06 Feb 2024 07:58:39 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jerin Jacob Date: Tue, 6 Feb 2024 21:28:13 +0530 Message-ID: Subject: Re: PMD for non PCI device To: Prashant Upadhyaya 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, 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 no= n > > > PCI/e device doing the ethernet packet i/o. > > > > > > Wanted to know if the above usecase is supported by DPDK infra and an= y > > > pointers on how one should go about writing a PMD for such a usecase > > > if supported. Would appreciate any inputs. > > > > > Hi, > > > > yes, such a usecase is supported, but the specifics of how to go about = it > > will vary depending on the type of PMD it is. DPDK already supports a r= ange > > 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 case > > 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 writi= ng 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 n= ot > > 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