From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>, "Ruifeng Wang" <ruifeng.wang@arm.com>,
<bruce.richardson@intel.com>, <konstantin.v.ananyev@yandex.ru>
Cc: <olivier.matz@6wind.com>
Subject: 32 bit arch optimization suggestion
Date: Fri, 25 Aug 2023 11:40:32 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87B3C@smartserver.smartshare.dk> (raw)
I was wondering...
How widely is DPDK used with 32 bit architectures?
Both phys_addr_t and rte_iova_t are cast as uint64_t in rte_common.h. Should they be uint32_t on 32 bit arch?
If so, the rte_mbuf structure has 12 unused byte in the first cache line on 32 bit arch.
Now, moving the "next" (4 byte pointer) and "tx_offload" (8 byte flags) fields to the first cache line could improve performance significantly, because this modification would leave the second cache line unused in most cases.
Med venlig hilsen / Kind regards,
-Morten Brørup
next reply other threads:[~2023-08-25 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 9:40 Morten Brørup [this message]
2023-08-25 9:50 ` Bruce Richardson
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=98CBD80474FA8B44BF855DF32C47DC35D87B3C@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=olivier.matz@6wind.com \
--cc=ruifeng.wang@arm.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).