DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: <santosh.shukla@caviumnetworks.com>
Cc: <olivier.matz@6wind.com>, <dev@dpdk.org>,
	<thomas.monjalon@6wind.com>, <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] mempool: Introduce _populate_mz_range api
Date: Fri, 20 Jan 2017 20:08:06 +0530	[thread overview]
Message-ID: <20170120143805.GA5741@localhost.localdomain> (raw)
In-Reply-To: <1484922017-26030-1-git-send-email-santosh.shukla@caviumnetworks.com>

On Fri, Jan 20, 2017 at 07:50:17PM +0530, santosh.shukla@caviumnetworks.com wrote:
> From: Santosh Shukla <santosh.shukla@caviumnetworks.com>
>  
> +/*
> + * wrapper to populate mz's pa/va addr range and len info to external
> + * mempool. HW mempool implementation to cache-in this inforamation
> + * in their local data structure.
> + * Note: api always get called before ops_alloc().
> + * */
> +void
> +rte_mempool_ops_populate_mz_range(struct rte_mempool *mp,
> +				  const struct rte_memzone *mz)
> +{
> +	struct rte_mempool_ops *ops;
> +
> +	ops = rte_mempool_get_ops(mp->ops_index);
> +	return ops->populate_mz_range(mp, mz);

Check for the NULL before calling the function pointer.

  reply	other threads:[~2017-01-20 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 14:20 santosh.shukla
2017-01-20 14:38 ` Jerin Jacob [this message]
2017-01-20 15:13 ` [dpdk-dev] [PATCH v2] " santosh.shukla
2017-01-31 10:31   ` Olivier Matz
2017-01-31 14:32     ` Santosh Shukla
2017-02-06 17:01       ` Olivier Matz
2017-02-07  4:00         ` Santosh Shukla

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=20170120143805.GA5741@localhost.localdomain \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=olivier.matz@6wind.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=thomas.monjalon@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).