[dpdk-dev] [PATCH 0/4] mbuf: Add new private data area accessor function.

[Dan Gora]

Hi All,

Below is a series of patches to add a new API function to allow DPDK
applications to access the private data area of the mbuf, if one exists.

This eliminates the repeated code in applications to access the private
data area and makes the API a bit more complete, since there are already
accessor functions to access the start of the buffer, the start of data, etc.

One question I had about was the name...

What are the rules for naming mbuf APIs?  When should rte_mbuf_XX vs.
rte_pktmbuf_XX be used?

The first patch [1 of 4] adds the accessor function to rte_mbuf.h.

The other three patches clean up other code to use this new function.

Please let me know what you think.

thanks
dan


Dan Gora (4):
  mbuf: add accessor function for private data area
  examples/ipsec-secgw: use rte fcn to access private area
  examples/ipsec-secgw: use ipsec fcn to access private area
  vhost/crypto: use rte fcn to access private area

 examples/ipsec-secgw/ipsec.h    |  2 +-
 examples/ipsec-secgw/sa.c       |  2 +-
 lib/librte_mbuf/rte_mbuf.h      | 19 +++++++++++++++++++
 lib/librte_vhost/vhost_crypto.c |  6 ++----
 4 files changed, 23 insertions(+), 6 deletions(-)

-- 
2.17.0.582.gccdcbd54c4