32 is an even divisor of CLIB_CACHE_LINE_BYTES for every platform that I can think of.
The usual scheme: split the data across 2 (or more) elogs. Any special reason you can’t do that? Thanks… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Alex Salig Sent: Sunday, December 4, 2016 5:53 AM To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] Formatted elogs more than 20 bytes 1. I need to log some events with elog which requires more than 20 bytes, therefore I changed the vppinfra/vppinfra/elog.h file: u8 data[20]; --->> u8 data[52]; Then, I have build the VPP project and test elog. It has a little lower performance. But would it cause some bugs or runtime problems? 2. Why there is such 20 bytes limitation (or why event must be padded to 32 bytes)?
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
