On Mon, Feb 12, 2018 at 02:58:31PM +0100, Thomas Monjalon wrote: > 12/02/2018 12:23, Adrien Mazarguil: > > On Fri, Feb 09, 2018 at 05:39:50PM +0100, Thomas Monjalon wrote: > > > I think it's better to have some random thoughts than nothing. > > > All the comments you gave in this thread deserve to be written in > > > the documentation as soon as possible. > > > > Right, but as a side note in the meantime, more complete documentation is > > already available in Doxygen format in mlx4_flow.c. *All* limitations are > > also returned in plain text through error messages (rte_flow_error.message) > > in the same file (git grep 'msg =' drivers/net/mlx4/mlx4_flow.c). > > OK, so we can just point to this file in the documentation and we are done.
One remaining issue is that we do not generate documentation out of PMDs since they do not expose public APIs. We can still somehow point to their source code though. > [...] > > > Do you plan to provide a template or an example? > > > > I certainly would like to submit something with the plan I suggested, > > unfortunately I don't have time to work on that at the moment. > > Is it worth the effort, given it is already documented in code? I don't think it's super urgent but I definitely think it would still be useful, if only to summarize all quirks at once in one place instead of leaving users discover them through trial & error as only one error can be reported at once. Keep in mind not all features/limitations are documented in Doxygen format; PMDs are not forced to have one parse function per pattern item for instance. In mlx4, supported actions are handled by a common function and are not documented individually. -- Adrien Mazarguil 6WIND