Speaking mostly as a user, there is some really important information needed for using VPP, which is not documented (at all, or at least anywhere that can be found).
I would like to make a request that someone take up this request and provide documentation, and preferably add it (or a link to it) to the (overly sparse) FAQ list. Here is what IMHO is necessary to document: RSS (and related techniques/technologies such as RFS, RPS, MSI-X, queue to CPU affinity, etc). For example, if a NIC has been configured by way of ethtool before VPP takes over the NIC, what happens to any RSS-type configurations, including "ntuple" rules? If there is a plan for some of these things but no current code, this would also be good to document. There are some configuration file elements (CPU and worker numbers/counts, and dpdk device configuration for RX queues), but no indication how those interact, and no apparent explicit control. Ideally, it would be good to have the NIC itself handle the packet flow (to specific queues) for ntuple rules, IF the NIC supports it, rather than having to add explicit VPP Nodes for that. What my main concern is, is the ability to dedicate CPU(s) for specific kinds of flow, especially if the flow requires "punting" (or the vppsb/router or vppsb/netlink equivalents) for host stack stuff, like handling BGP packets to a non-VPP BGP speaker such as quagga or FRR or bird. But for now, documentation on how things work and how different configuration elements interact, would be a good start. Thanks, Brian
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13539): https://lists.fd.io/g/vpp-dev/message/13539 Mute This Topic: https://lists.fd.io/mt/32561940/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
