DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kyo.Liu" <kyo.liu@nebula-matrix.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
	"Chenbo Xia" <chenbox@nvidia.com>,
	"Nipun Gupta" <nipun.gupta@amd.com>, "dev" <dev@dpdk.org>
Subject: 回复:[PATCH v3 1/1] bus/pci: introduce get_iova_mode for pci dev
Date: Tue, 29 Apr 2025 11:08:15 +0800	[thread overview]
Message-ID: <46ce6637-7310-48da-9491-3628fd8115f9.kyo.liu@nebula-matrix.com> (raw)
In-Reply-To: <20250428085509.44197fba@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

Thank you for raising this important concern. 
To confirm: Our vendor driver (NBL PMD) is actively being upstreamed to DPDK. This patch is required for its coexistence implementation. We kindly request to merge this foundational change first to enable the driver submission.
We will follow up with the full NBL driver code within 4 weeks. 
Thank you for your consideration.

------------------------------------------------------------------
发件人:Stephen Hemminger <stephen@networkplumber.org>
发送时间:2025年4月28日(周一) 23:55
收件人:"Kyo.Liu"<kyo.liu@nebula-matrix.com>
抄 送:Thomas Monjalon<thomas@monjalon.net>; Chenbo Xia<chenbox@nvidia.com>; Nipun Gupta<nipun.gupta@amd.com>; dev<dev@dpdk.org>
主 题:Re: [PATCH v3 1/1] bus/pci: introduce get_iova_mode for pci dev


On Sun, 27 Apr 2025 02:27:34 +0000
Kyo Liu <kyo.liu@nebula-matrix.com> wrote:

> I propose this patch for DPDK to enable coexistence between
> DPDK and kernel drivers for regular NICs.This solution requires
> adding a new pci_ops in rte_pci_driver, through which DPDK will
> retrieve the required IOVA mode from the vendor driver.
> This mechanism is necessary to handle different IOMMU
> configurations and operating modes. Below is a detailed
> analysis of various scenarios:

The words "vendor driver" have me worried.
Is this a PMD that is being incorporated into DPDK or some out
of tree driver. If it is out of tree, such changes will be summarily rejected.
We don't accept changes that are unused in tree.


[-- Attachment #2: Type: text/html, Size: 1419 bytes --]

      reply	other threads:[~2025-04-29  3:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250427013611.150888-1-kyo.liu>
2025-04-27  2:27 ` [PATCH " Kyo Liu
2025-04-28 15:50   ` Stephen Hemminger
2025-04-28 15:55   ` Stephen Hemminger
2025-04-29  3:08     ` Kyo.Liu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46ce6637-7310-48da-9491-3628fd8115f9.kyo.liu@nebula-matrix.com \
    --to=kyo.liu@nebula-matrix.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=nipun.gupta@amd.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).