Re: [PATCH 0/4] rework mlx5 guide

[Thomas Monjalon <thomas@monjalon.net>]

18/07/2025 17:36, Stephen Hemminger:
> Looks better, it would be good to look at the table of contents
> (right column in html) to see if could be better in complex document
> like this.

Yes I've paid attention to the table of contents.
Thanks for the suggestions below.

> For example the Usage, dump flows, VF trusterd, etc all seem like
> FAQ kind of answers and could go under one heading.

I did not really change this part,
but you're right, I should add a common heading for those "usage" topics.

> The section about statistics should also get headers reset
> to the right level. The part about phy_ counters might be better
> in limitations section.

I didn't touch statistics.
This section is clearly not complete and should be updated later.

> The Limitations should probably be at
> a different section level, not stuck after live migration.

You are probably talking about the multiprocess section.

> It would be good to explain a little more about "forked secondary
> process". I think this is a general thing across all of DPDK
> not MLX5 specific. Should this go in EAL?

Yes, and there are things which could go in ethdev doc as well.
The goal of this series is to have a good skeleton to work with.
Some content could be moved outside and referenced with a link
in future patches.

> The part about Rx/Tx tuning and Rx burst function might be better
> together.

Right, I'll move.