From: Stephen Hemminger <stephen@networkplumber.org>
To: Mike Davison <mike.davison.tech@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] mempools
Date: Tue, 17 Jan 2017 15:23:57 -0800 [thread overview]
Message-ID: <20170117152357.7d2b87ff@xeon-e3> (raw)
In-Reply-To: <CAE3cmzDTvGEqAzKY64rGWh4sXsNnAb74DkRKp+ZOYXvv4KLrPQ@mail.gmail.com>
On Tue, 17 Jan 2017 15:13:41 -0800
Mike Davison <mike.davison.tech@gmail.com> wrote:
> Looking at memory pools. It looks like they are a fixed size and cannot be
> changed. Correct?
>
> Assuming my reading is correct, is there interest in adding
> dynamically-sized memory pools? I would envision these memory pools having
> fixed-sized elements, as they do today, but resizing the number of
> fixed-sized elements, within some limits, as needed. Good? Bad?
>
> Thanks,
> Mike
Memzone's are fixed size regions
Mempool's are fixed size objects based on memzone's
For variable size objects, use rte_malloc
next prev parent reply other threads:[~2017-01-17 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 23:13 Mike Davison
2017-01-17 23:23 ` Stephen Hemminger [this message]
2017-01-17 23:32 ` Mike Davison
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=20170117152357.7d2b87ff@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=mike.davison.tech@gmail.com \
--cc=users@dpdk.org \
/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).