20/03/2020 07:49, Jerin Jacob: > On Tue, Mar 17, 2020 at 7:16 PM Wisam Jaddo <wis...@mellanox.com> wrote: > > Thanks for this application. Useful stuff. > > > > > Introducing new application for rte_flow performance > > testing. The application provide the ability to test > > insertion rate of specific rte_flow rule, by stressing > > it to the NIC, and calculate the insertion rate. > > > > It also provides packet per second measurements > > after the insertion operation is done. > > > > The application offers some options in the command > > line, to configure which rule to apply. > > > > After that the application will start producing rules > > with same pattern but increasing the outer IP source > > address by 1 each time, thus it will give different > > flow each time, and all other items will have open masks. > > > > The current design have single core insertion rate. > > In the future we may have a multi core insertion rate > > measurement support in the app. > > If I understand correctly, > # On the main thread, this application first check the flow insertion > performance > # and then start the worker thread for packet forwarding. > Why this application testing the packet forwarding?, We already have > testpmd for that.
I think it is interesting to measure forwarding performance when million of flow rules are in effect. > IMO, This application needs to focus only on > - Insertion performance > - Deletion performance > - IMO, it is better to add a framework for the profile where the first > version of this application can > define common a set of ITEMS and set of ACTION and later others can extend it. > And the framework can run over all the profiles and spit out the > insertion and deletion > performance. What do you call a profile? Is it a set of rules? I think this first version is proposing rules customization with parameters. Note: I prefer a non-interactive application for performance testing. > > The app supports single and multi core performance > > measurements.
