DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dan Gora <dg@adax.com>
To: dev@dpdk.org
Cc: Dan Gora <dg@adax.com>
Subject: [dpdk-dev] [PATCH v2 0/4] mbuf: Add new private data area accessor function.
Date: Mon, 18 Jun 2018 16:34:41 -0700	[thread overview]
Message-ID: <20180618233441.21323-1-dg@adax.com> (raw)

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.

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

v2:
* Change 'md' to 'm' in rte_mbuf_to_priv().
* Remove check of m->priv_len in rte_mbuf_to_priv() to avoid confusion
  if used with indirect mbufs.


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      | 18 ++++++++++++++++++
 lib/librte_vhost/vhost_crypto.c |  6 ++----
 4 files changed, 22 insertions(+), 6 deletions(-)

-- 
2.18.0.rc1.1.g6f333ff2f

                 reply	other threads:[~2018-06-18 23:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180618233441.21323-1-dg@adax.com \
    --to=dg@adax.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).