From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Dan Gora <dg@adax.com>, dev@dpdk.org
Cc: Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 1/4] mbuf: add accessor function for private data area
Date: Fri, 8 Jun 2018 09:30:17 +0100 [thread overview]
Message-ID: <8f40b27d-50b7-4601-ee92-0c04c7230b26@intel.com> (raw)
In-Reply-To: <20180607235454.27832-1-dg@adax.com>
On 08-Jun-18 12:54 AM, Dan Gora wrote:
> Add an inline accessor function to return the starting address of
> the private data area in the supplied mbuf.
>
> If the user did not allocate space for a private data area in the
> mbuf's memory pool, then return NULL.
>
> This allows applications to easily access the private data area
> between the struct rte_mbuf and the data buffer in the specified mbuf
> without creating private macros or accessor functions.
>
> Signed-off-by: Dan Gora <dg@adax.com>
> ---
<...>
> +static inline void *
> +rte_mbuf_to_priv(struct rte_mbuf *md)
> +{
> + if (md->priv_size == 0)
> + return NULL;
> +
> + return RTE_PTR_ADD(md, sizeof(struct rte_mbuf));
> +}
Hi Dan,
New API's should be marked as __rte_experimental for at least one release.
> +
> /**
> * Returns TRUE if given mbuf is cloned by mbuf indirection, or FALSE
> * otherwise.
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-06-08 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 23:54 Dan Gora
2018-06-08 8:30 ` Burakov, Anatoly [this message]
2018-06-08 9:06 ` Andrew Rybchenko
2018-06-08 17:19 ` Wiles, Keith
2018-06-09 0:24 ` Dan Gora
2018-06-09 9:23 ` Andrew Rybchenko
2018-06-12 2:24 ` Dan Gora
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=8f40b27d-50b7-4601-ee92-0c04c7230b26@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=dg@adax.com \
--cc=olivier.matz@6wind.com \
/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).