DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Andrew Bailey <abailey@iol.unh.edu>
Cc: luca.vizzarro@arm.com, dev@dpdk.org, dmarx@iol.unh.edu
Subject: Re: [PATCH v5] dts: enable port binding on the TG
Date: Mon, 22 Sep 2025 11:46:27 -0400	[thread overview]
Message-ID: <CAJvnSUD5raC7qtXzD7v11wHR0r2XG4+5hm+UcCPo7H+Oa=QuFA@mail.gmail.com> (raw)
In-Reply-To: <20250910122749.8277-1-abailey@iol.unh.edu>

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

On Wed, Sep 10, 2025 at 8:30 AM Andrew Bailey <abailey@iol.unh.edu> wrote:

> Currently, ports on the TG are not bound to the correct drivers prior to
> running DTS. This causes DTS to crash if they are not initially bound to
> the intended drivers. Binding the TG ports to the proper driver caused
> DTS to fail when the OS and DPDK drivers were the same, due to the port
> link not being up.


This probably does not read very clearly to people not working on DTS. I
would be more "to the point" by saying something like "Currently, DTS will
not attempt to bind the TG interfaces to the kernel driver automatically,
meaning the user must manually verify the TG binding before running DTS.
Also, when the TG and DPDK drivers are the same, DTS will not automatically
attempt to bring up the link on the TG port. So, this change adds both of
these automatic steps for the TG."


> Changing the bound_for_dpdk method for a port to
> return false when the OS driver and DPDK driver were shared on a TG
> node allowed the TG ports to enter the logic to be brought up in the
> configure_ports method within the topology class.
>

I believe this is a carry over from your V3. The V4 and V5 patches do not
include this change to the bound_for_dpdk property.

Otherwise, the commit looks good, thank you! I will tweak the commit
message itself per my preferences above when I merge to next-dts.

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

  parent reply	other threads:[~2025-09-22 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 18:21 [PATCH 1/2] dts: introduce abstract class for TG and SUT DPDK runtime environments Andrew Bailey
2025-08-08 18:21 ` [PATCH 2/2] dts: enable port binding on the TG Andrew Bailey
2025-08-28 12:37   ` [PATCH v3] " Andrew Bailey
2025-08-28 12:50     ` Luca Vizzarro
2025-08-28 15:17       ` Andrew Bailey
2025-08-28 12:54     ` Patrick Robb
2025-09-02 16:52     ` Luca Vizzarro
2025-09-04 16:25       ` Patrick Robb
2025-09-08 17:36   ` [PATCH v4] " Andrew Bailey
2025-09-09 15:39     ` Luca Vizzarro
2025-09-10 12:27   ` [PATCH v5] " Andrew Bailey
2025-09-11 13:24     ` Luca Vizzarro
2025-09-22 15:46     ` Patrick Robb [this message]
2025-09-22 21:45       ` Patrick Robb
2025-08-11 11:17 ` [PATCH 1/2] dts: introduce abstract class for TG and SUT DPDK runtime environments Luca Vizzarro

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='CAJvnSUD5raC7qtXzD7v11wHR0r2XG4+5hm+UcCPo7H+Oa=QuFA@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=abailey@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=luca.vizzarro@arm.com \
    /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).