From: Stephen Hemminger <stephen@networkplumber.org>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: olivier.matz@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mbuf: replace c memcpy() code semantics with optimized rte_memcpy()
Date: Tue, 28 Jul 2020 10:46:24 -0700 [thread overview]
Message-ID: <20200728104624.3541fba8@hermes.lan> (raw)
In-Reply-To: <20200723070240.14749-1-sarosh.arif@emumba.com>
On Thu, 23 Jul 2020 12:02:40 +0500
Sarosh Arif <sarosh.arif@emumba.com> wrote:
> Since rte_memcpy is more optimized it should be used instead of memcpy
>
> Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
The part in pkmbuf_pool_init is not performance critical.
The layout of rte_mbuf_dynfield is sub optimal.
struct rte_mbuf_dynfield {
char name[64]; /* 0 64 */
/* --- cacheline 1 boundary (64 bytes) --- */
size_t size; /* 64 8 */
size_t align; /* 72 8 */
unsigned int flags; /* 80 4 */
/* size: 88, cachelines: 2, members: 4 */
/* padding: 4 */
/* last cacheline: 24 bytes */
};
1. It should have been sized so that overall it was 64 bytes.
2. Use 8 bytes for size and align is wasteful.
3. Hold 4 bytes for future flags is also wasteful. YAGNI
If you look at assembly output on x86 the copy of params becomes a sequence
of vmovups instructions with Gcc.
For 20.11 maybe:
diff --git a/lib/librte_mbuf/rte_mbuf_dyn.h b/lib/librte_mbuf/rte_mbuf_dyn.h
index 8407230ecfdc..eb1d01f97f40 100644
--- a/lib/librte_mbuf/rte_mbuf_dyn.h
+++ b/lib/librte_mbuf/rte_mbuf_dyn.h
@@ -70,16 +70,16 @@
/**
* Maximum length of the dynamic field or flag string.
*/
-#define RTE_MBUF_DYN_NAMESIZE 64
+#define RTE_MBUF_DYN_NAMESIZE 60
/**
* Structure describing the parameters of a mbuf dynamic field.
*/
struct rte_mbuf_dynfield {
char name[RTE_MBUF_DYN_NAMESIZE]; /**< Name of the field. */
- size_t size; /**< The number of bytes to reserve. */
- size_t align; /**< The alignment constraint (power of 2). */
- unsigned int flags; /**< Reserved for future use, must be 0. */
+ uint8_t size; /**< The number of bytes to reserve. */
+ uint8_t align; /**< The alignment constraint (power of 2). */
+ uint16_t flags; /**< Reserved for future use, must be 0. */
};
/**
Or make the dynamic field dynamic size to avoid wasting space?
prev parent reply other threads:[~2020-07-28 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 7:02 Sarosh Arif
2020-07-23 15:47 ` Stephen Hemminger
2020-07-28 13:30 ` Sarosh Arif
2020-07-28 13:50 ` Olivier Matz
2020-07-28 17:46 ` Stephen Hemminger [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=20200728104624.3541fba8@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=sarosh.arif@emumba.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).