DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vithal S Mohare <vmohare@arubanetworks.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Walk through a given mbuf-pool elements
Date: Mon, 15 Dec 2014 10:38:58 +0000	[thread overview]
Message-ID: <98DB008FA2AC6644B40AD8C766FAB271014BDE0FE7@BOREAL.arubanetworks.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258213BFB08@IRSMSX105.ger.corp.intel.com>

Hi Konstantin,

Thanks for the reply.
I was trying to find more intuitive one compare to rte_mempool_obj_iter().  Once mempool is created with objects, shouldn't we able to walk-through by just passing 'mp' object and avoiding other params like vaddr, elt_size etc.   For now, I could use callback called during mempool creation itself.


Thanks,
-Vithal

-----Original Message-----
From: Ananyev, Konstantin [mailto:konstantin.ananyev@intel.com] 
Sent: Monday, December 15, 2014 3:42 PM
To: Vithal S Mohare; dev@dpdk.org
Subject: RE: Walk through a given mbuf-pool elements

Hi Vithal,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vithal S Mohare
> Sent: Monday, December 15, 2014 5:08 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Walk through a given mbuf-pool elements
> 
> [Re-sending the mail after registering to dpdk.org] Team,
> 
> I am looking for a code/api to walk through a dpdk mbuf-pool elements (similar to rte_mempool_walk() but for elements within
> mempool).   Calling pkt_mbuf_alloc for 'n' elements and then _free is not an option.  Rte_mempool_obj_itr() walks through, but does
> lot more than walking itself.   Please suggest if anybody has better alternatives.

Not sure why rte_mempool_obj_iter() wouldn't work for you?
It just walks through all elements of the pool and for ach calls a user provided callback.
Nothing else.

Konstantin

> 
> Thanks,
> -Vithal

      reply	other threads:[~2014-12-15 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  5:07 Vithal S Mohare
2014-12-15 10:11 ` Ananyev, Konstantin
2014-12-15 10:38   ` Vithal S Mohare [this message]

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=98DB008FA2AC6644B40AD8C766FAB271014BDE0FE7@BOREAL.arubanetworks.com \
    --to=vmohare@arubanetworks.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.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).