Skip to content

feat(linux): Add Ethernet performance numbers for 12.01 release - #774

Merged
praneethbajjuri merged 1 commit into
TexasInstruments:masterfrom
danish-ti:12.1-eth-perf
Aug 11, 2026
Merged

feat(linux): Add Ethernet performance numbers for 12.01 release#774
praneethbajjuri merged 1 commit into
TexasInstruments:masterfrom
danish-ti:12.1-eth-perf

Conversation

@danish-ti

Copy link
Copy Markdown
Contributor

Add netperf Ethernet performance data for AM62X, AM62PX, AM62LX and AM64X in their respective performance guide RST files. Each section covers CPSW TCP bidirectional throughput (with and without interrupt pacing) and UDP egress/ingress 0-loss throughput across 64/128/256/ 1024/1518B frame sizes. AM64X additionally includes ICSSG results.

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown

New warnings found with rstcheck:

source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:507: (ERROR/3) Inconsistent title style: skip from level 4 to 6.
source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:521: (ERROR/3) Inconsistent title style: skip from level 4 to 6.
source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:535: (ERROR/3) Inconsistent title style: skip from level 4 to 6.

Add netperf Ethernet performance data for AM62X, AM62PX, AM62LX and
AM64X in their respective performance guide RST files. Each section
covers CPSW TCP bidirectional throughput (with and without interrupt
pacing) and UDP egress/ingress 0-loss throughput across 64/128/256/
1024/1518B frame sizes. AM64X additionally includes ICSSG results.

Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
Comment thread source/devices/AM62X/linux/Linux_Performance_Guide.rst
Comment thread source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst
@StaticRocket

Copy link
Copy Markdown
Member

Ugh, alright. I'll look at fixing those good awful templates again. Change the am64 document to match the others for now, assuming that makes the TOC tree happy. Test it locally and make sure it's not trying to put that section above anything else in the hierarchy.

@danish-ti

Copy link
Copy Markdown
Contributor Author

Ugh, alright. I'll look at fixing those good awful templates again. Change the am64 document to match the others for now, assuming that makes the TOC tree happy. Test it locally and make sure it's not trying to put that section above anything else in the hierarchy.

@StaticRocket If I change the AM64 document to match the others, rstcheck fails with "Title level inconsistent" erros.
source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:507: (SEVERE/4) Title level inconsistent: source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:521: (SEVERE/4) Title level inconsistent: source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:535: (SEVERE/4) Title level inconsistent:
This happens because AM64 already uses " for Level 5 headings. Changing AM64 breaks its existing hierarchy. To fix this and keep everything consistent across the PR, I suggest we update the AM62 files (am62x, am62l, am62p) to use " for Level 5 instead. This resolves the warnings and standardises the templates.

@StaticRocket

Copy link
Copy Markdown
Member

The problem with that is, that requires more changes that go explicitly against the section hierarchy outlined in the contribution guide.

@danish-ti

danish-ti commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

@StaticRocket

  1. Keeping " as level 5 for both AM64 and AM62 docs requires more changes that go explicitly against the section hierarchy outlined in the contribution guide.
  2. Keeping ~ as level 5 for both AM64 and AM62 docs introduces rstcheck warnings. source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:507: (SEVERE/4) Title level inconsistent: source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:521: (SEVERE/4) Title level inconsistent: source/devices/AM64X/linux/RT_Linux_Performance_Guide.rst:535: (SEVERE/4) Title level inconsistent:
  3. Keeping ~ in AM62x and " in AM64x satisfies both 1 and 2 but creates inconsistency across docs.
  4. Implement point 2 but to avoid rstwarnings, we need to change EMMC EXT4 and other level 5 from " to ~. I didn't want to touch anything not related to networking in this PR.

What do you think should be done here then? The current state of PR is 3.

@StaticRocket

Copy link
Copy Markdown
Member

Eh. If the linter is happy for now then it's fine as is. I have a pending PR reworking that template file again.

@danish-ti

Copy link
Copy Markdown
Contributor Author

Hi @praneethbajjuri Can you please approve this so that @StaticRocket can merge this PR?

@StaticRocket

Copy link
Copy Markdown
Member

Overhauled the template for these files so it won't be an issue in the future. Not sure when we want to re-sync em.

@praneethbajjuri
praneethbajjuri merged commit fbb9d70 into TexasInstruments:master Aug 11, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants