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

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.)

and some bits around:

http://dpdk.org/ml/archives/dev/2016-May/038390.html
http://dpdk.org/ml/archives/dev/2016-April/037509.html
http://dpdk.org/ml/archives/dev/2016-April/037457.html
http://dpdk.org/ml/archives/dev/2016-April/036979.html

...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?

Regards
Jan

-- 
   Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic

             reply	other threads:[~2016-05-17 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 12:34 Jan Viktorin [this message]
2016-05-17 13:56 ` Olivier MATZ
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=20160517143432.48e5a305@pcviktorin.fit.vutbr.cz \
    --to=viktorin@rehivetech.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).