Hmmm, yeah. Been at this for years, I can’t really remember when we settled on e.g. n_vectors vs. n_vector_elts or some such.
In new code, it’s perfectly fair to use whatever names seem fit for purpose. Vlib would be happy doing image processing, or any other kind of vector processing. There’s no law which says that frames need to have 32-bit elements. Each node decides. FWIW... Dave From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Christian Hopps Sent: Monday, March 30, 2020 8:07 PM To: vpp-dev <vpp-dev@lists.fd.io> Cc: Christian Hopps <cho...@chopps.org> Subject: [vpp-dev] n_vectors... Something has always bothered me about my understanding of VPPs use of the term "vector" and "vectors". When I think of Vector Packet Processing I think of processing a vector (array) of packets in a single call to a node. The code, though, then seems to refer to the individual packets as "vectors" when it uses field names like "n_vectors" to refer to the number of buffers in a frame, or when "show runtime" talks about "vectors per call", when I think it's really talking about "packets/buffers per call" (and my mind wants to think that it's always *1* vector/frame of packets per call by design). I find this confusing, and so I thought I'd ask if there was some meaning here I'm missing? Thanks, Chris.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15951): https://lists.fd.io/g/vpp-dev/message/15951 Mute This Topic: https://lists.fd.io/mt/72667316/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
