From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: [dpdk-dev] Limiting packet buffers under 4GB
Date: Mon, 4 Nov 2019 12:59:40 +0000 [thread overview]
Message-ID: <BYAPR18MB2424E2396F4B352EDC80488AC87F0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
Hi Anatoly and All,
Just wondering what would the side effect of lowering a _bit_ of static uint64_t baseaddr = 0x100000000 in
lib/librte_eal/common/eal_common_memory.c for 64bit systems.
Use case:
If we _reserve_ VA address which less than 2^32 ONLY for packet buffers(mbuf), The use cases like
Pipeline, where need to transfer packets from one core to another cores can use ring element
size of 4B(32bit) which will reduce the a lot of read and write to enable better
performance.
i.e Since upper 32bits will be zero, it is matter of typecasting of item to read and write from/to ring.
Essentially memcpy overhead for moving pointers over the ring will be half.
Is baseaddr set to 2^32 to make sure that secondary process will have more _chance_ of getting
the baseaddr in order for DPDK to work?
Thoughts on above? On general to reduce the mbuf pointer storage requirement for ring?
next reply other threads:[~2019-11-04 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 12:59 Jerin Jacob Kollanukkaran [this message]
2019-11-04 15:19 ` Olivier Matz
2019-11-06 12:16 ` Burakov, Anatoly
2019-11-06 12:39 ` Jerin Jacob
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=BYAPR18MB2424E2396F4B352EDC80488AC87F0@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@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).