From: Dmitry Vyal <dmitryvyal@gmail.com>
To: Robert Sanford <rsanford@prolexic.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How to fight forwarding performance regression on large mempool sizes.
Date: Sun, 22 Sep 2013 23:03:40 +0400 [thread overview]
Message-ID: <523F3F0C.2010104@gmail.com> (raw)
In-Reply-To: <CAFmpvUNEtcM8TtHJhqShRggDKRT3Y0vAY9aiG=28aV9NomQRgA@mail.gmail.com>
On 09/20/2013 07:34 PM, Robert Sanford wrote:
> One more point, if you're not doing this already: Allocate 2^N-1
> mbufs, not 2^N. According to the code and comments: "The optimum size
> (in terms of memory usage) for a mempool is when n is a power of two
> minus one: n = (2^q - 1)."
>
Many thanks! Didn't know about it.
prev parent reply other threads:[~2013-09-22 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 7:50 Dmitry Vyal
2013-09-19 19:39 ` Robert Sanford
2013-09-19 19:43 ` Venkatesan, Venky
2013-09-20 6:50 ` Dmitry Vyal
2013-09-20 6:48 ` Dmitry Vyal
2013-09-20 14:41 ` Robert Sanford
2013-09-20 15:34 ` Robert Sanford
2013-09-22 19:03 ` Dmitry Vyal [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=523F3F0C.2010104@gmail.com \
--to=dmitryvyal@gmail.com \
--cc=dev@dpdk.org \
--cc=rsanford@prolexic.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).