I've been using VPP for over 6 months, and read every scrap of documentation available...
This request was due to lack of clear information on RSS actuals, rather than unclear specifications on what configuration items are available. It is kind of impossible to tell what is going on, either via all the VPP (and vppctl) commands and configs, or from the host OS, or from external things like test/measurement devices. SInce VPP puts all the allocated CPUs into poll mode, and effectively runs them at 100% CPU, it is not possible to determine whether any particular CPU is receiving packets, or the observed soft interrupt rates, or anything. Thanks, Brian On Mon, Jul 22, 2019 at 3:11 PM John DeNisco (jdenisco) <jdeni...@cisco.com> wrote: > > Brian, > > > > The best place to get started with VPP is to look at the documentation at > > > > https://fdio-vpp.readthedocs.io/en/latest/index.html > > > > Once VPP is installed the descriptions of the parameters can be found in > the startup file located in /etc/vpp/startup.conf. > > > > Does this help? > > > > John > > > > > > *From: *<vpp-dev@lists.fd.io> on behalf of Brian Dickson < > brian.peter.dick...@gmail.com> > *Date: *Monday, July 22, 2019 at 2:12 PM > *To: *"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> > *Subject: *[vpp-dev] FAQ or Documentation request > > > > 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 (#13541): https://lists.fd.io/g/vpp-dev/message/13541 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] -=-=-=-=-=-=-=-=-=-=-=-
