There is no chance that such a patch would be merged on my watch. Please allocate your use-case-specific metadata from a pool, and carry the metadata pool index in opaque2 (or opaque, if you can swing it).
Bloating the vlib_buffer_t to carry use-case-specific metadata is a non-starter. Dave From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Satya Murthy Sent: Tuesday, March 3, 2020 11:12 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] Can i increase the size of vlib buffer opaque2 We are currently using opaque2 which has 10 uint32. Can i increase this size to 30 uint32s. What kind of impact/restrictions we have for this opaque2 metadata sizes. Please let us know. -- Thanks & Regards, Murthy
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15682): https://lists.fd.io/g/vpp-dev/message/15682 Mute This Topic: https://lists.fd.io/mt/71703548/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
