From: Hangbin Liu <liuhangbin@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, "Abdul Rahim,
Faizal" <faizal.abdul.rahim@linux.intel.com>
Subject: Re: [RFC PATCH for-faizal 0/4] tc-taprio selftests
Date: Fri, 22 Dec 2023 14:28:45 +0800 [thread overview]
Message-ID: <ZYUsnTuoUi2qCdLj@Laptop-X1> (raw)
In-Reply-To: <20231221132521.2314811-1-vladimir.oltean@nxp.com>
On Thu, Dec 21, 2023 at 03:25:17PM +0200, Vladimir Oltean wrote:
> Unfortunately the isochron version from debian will not work on veth
> pairs, I had to make some changes and add the --omit-hwts option to
> the sender and receiver programs. The modified version is on this branch
> here, I will merge the changes to 'master' once I have enough confidence
> in them.
> https://github.com/vladimiroltean/isochron/tree/omit-hwts
>
> For testing the tc-taprio software scheduling path, we don't need PTP
> synchronization or hardware timestamps anyway.
>
> This is just a skeleton that I'm hoping Faizal can pick up and extend
> with more test cases for dynamic schedule changes. It should run
> primarily on the veth driver, but should behave the same on any network
> driver as well, including those who also have tc-taprio offload.
Tested-by: Hangbin Liu <liuhangbin@gmail.com>
Reviewed-by: Hangbin Liu <liuhangbin@gmail.com>
prev parent reply other threads:[~2023-12-22 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:25 [RFC PATCH for-faizal 0/4] tc-taprio selftests Vladimir Oltean
2023-12-21 13:25 ` [RFC PATCH for-faizal 1/4] selftests: net: forwarding: allow veth pairs to be created with multiple queues Vladimir Oltean
2023-12-21 13:25 ` [RFC PATCH for-faizal 2/4] selftests: net: tsn: push --txtime out of isochron_do() Vladimir Oltean
2023-12-21 13:25 ` [RFC PATCH for-faizal 3/4] selftests: net: tsn: allow isochron_do() to skip sync monitoring on sender too Vladimir Oltean
2023-12-21 13:25 ` [RFC PATCH for-faizal 4/4] selftests: net: tsn: add tc-taprio test cases (WIP) Vladimir Oltean
2023-12-22 6:28 ` Hangbin 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=ZYUsnTuoUi2qCdLj@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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