DPDK patches and discussions
 help / color / mirror / Atom feed
From: jspewock@iol.unh.edu
To: Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
	thomas@monjalon.net, wathsala.vithanage@arm.com,
	probb@iol.unh.edu, paul.szczepanek@arm.com,
	yoan.picchi@foss.arm.com
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v2 0/1] dts: Add the ability to bind ports to drivers
Date: Thu,  9 Nov 2023 17:57:57 -0500	[thread overview]
Message-ID: <20231109225857.23741-2-jspewock@iol.unh.edu> (raw)

From: Jeremy Spewock <jspewock@iol.unh.edu>

Changes in this version address the comments on the last and change what
was necessary. Now, we no longer modprobe the driver, but the decision
was made to still make driver binding exclusive to the SUT for the time
being due to the uncertainty of what binding drivers on the traffic
generator will look like in the future when we need to do so.

I also decided to leave the os_udp test case in the patch as leaving it
does no harm really, all that is required for it to run is binding to
the os_driver before it runs and back to the DPDK driver after, and I
think it serves as somewhat of a "hello world" for ensuring that your
traffic generator is functioning. If it is decided that we no longer
want it in the future or want to make it a part of the hello_world
suite, another patch will be submitted at a later date.

v1: https://mails.dpdk.org/archives/dev/2023-November/281477.html

Jeremy Spewock (1):
  dts: allow configuring MTU of ports

 dts/framework/remote_session/linux_session.py | 7 +++++++
 dts/framework/remote_session/os_session.py    | 9 +++++++++
 2 files changed, 16 insertions(+)

-- 
2.42.0


             reply	other threads:[~2023-11-09 22:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 22:57 jspewock [this message]
2023-11-09 22:57 ` [PATCH v2 1/1] dts: allow configuring MTU of ports jspewock

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=20231109225857.23741-2-jspewock@iol.unh.edu \
    --to=jspewock@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@arm.com \
    --cc=yoan.picchi@foss.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).