DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz@6wind.com>
To: Jan Viktorin <viktorin@rehivetech.com>, dev@dpdk.org
Cc: David Hunt <david.hunt@intel.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] What is the status of mempool manager?
Date: Tue, 17 May 2016 15:56:32 +0200	[thread overview]
Message-ID: <573B2310.60907@6wind.com> (raw)
In-Reply-To: <20160517143432.48e5a305@pcviktorin.fit.vutbr.cz>

Hi Jan,

On 05/17/2016 02:34 PM, Jan Viktorin wrote:
> Hello,
>
> I was trying to find out the status of the mempool rework and found
> this 36-pieces long patch set:
>
> http://dpdk.org/ml/archives/dev/2016-April/037464.html
>
> (I failed to apply it to 16.04, 2.1.0, current HEAD.)

It should be integrated soon, as there was no comment during
some time. I'll send a new version that applies on head
+ minor cosmetic changes.

> and some bits around:
>
> http://dpdk.org/ml/archives/dev/2016-May/038390.html

I need to review this one, it's on my todo list.

> http://dpdk.org/ml/archives/dev/2016-April/037509.html

I think the code is ready to be integrated, but I was expecting
some reactions on the v4, especially some precisions about the
use cases and the needs. See in the link "Things that should
still be discussed".

> http://dpdk.org/ml/archives/dev/2016-April/037457.html

It is integrated since today ;)

> http://dpdk.org/ml/archives/dev/2016-April/036979.html

Some comments have been done by Konstantin and myself, I
think a new version will be submitted. It will be integrated
in 16.07.

> ...but I am confused.
>
> I am trying to find out how to write a custom memory pool based on
> the uio_dmem_genirq driver. It provides DMA memory via the UIO API
> (maps).
>
> If I have a PMD running of top of this UIO, I need to implement a
> custom allocator that gets memory from the dev->mem_resource (with
> the mappings preloaded from the UIO by EAL).
>
> This is related to the SoC infra as given here:
>
> http://dpdk.org/ml/archives/dev/2016-May/038486.html
>
> Any idea how to start with this?

I think your feedback would be very valuable.

The "external mempool manager" series allows to register new
handler that replaces the internal ring storing the objects. It
does not change the way the memory is allocated.

The big patchset introduce new way of allocating memory used by
memory pool (no need to be virtually contiguous anymore). You
could throw an eye on rte_mempool_populate*() functions that
populate a mempool with memory for storing the objects.

I'm not sure I'm getting your exact needs.
Do you need to populate a ring-based mempool with specific memory,
retrieved from UIO API?
Do you need to replace the default internal ring by something else?
Do you need to access the mempool from the hardware?

Regards,
Olivier

  reply	other threads:[~2016-05-17 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 12:34 Jan Viktorin
2016-05-17 13:56 ` Olivier MATZ [this message]
2016-05-17 17:29   ` Jan Viktorin

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=573B2310.60907@6wind.com \
    --to=olivier.matz@6wind.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=viktorin@rehivetech.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).