Hello Bruce, I'm a little bit concerned about performance issues that would arise if these fields would go to the 2nd cache line.
For exampe, l2_len and l3_len fields are used by librte_ip_frag to find L3 and L4 headers position inside mbuf data. Thus, these values should be calculated by NIC offload, or by user on RX leg. Secondly, (I wouldn't say on behalf of everyone, but) we use these fields in our libraries as well for needs of classification. For instance, in case you try to support other ethertypes which are not supported by NIC offload (MPLS, IPX etc), but you still need to point out L3 and L3 headers. If my concerns are consistent, what would be possible suggestions? 03.09.2014 21:49, Bruce Richardson ?????: > The l2_len and l3_len fields are used for TX offloads and so should be > put on the second cache line, along with the other fields only used on > TX. > > Signed-off-by: Bruce Richardson <bruce.richardson at intel.com> -- Sincerely, Yerden Zhumabekov STS, ACI Astana, KZ
