From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] eal: fix 64bit address alignment in 32-bit builds
Date: Fri, 28 Apr 2017 10:56:56 +0200 [thread overview]
Message-ID: <1797441.atIi8ZZIaG@xps> (raw)
In-Reply-To: <20170428081551.28954-1-bruce.richardson@intel.com>
28/04/2017 10:15, Bruce Richardson:
> On i686 builds, the uint64_t type is 64-bits in size but is aligned to
> 32-bits only. This causes mbuf fields for rearm_data to not be 16-byte
> aligned on 32-bit builds, which causes errors with some vector PMDs which
> expect the rearm data to be aligned as on 64-bit.
>
> Given that we cannot use the extra space in the data structures anyway, as
> it's already used on 64-bit builds, we can just force alignment of physical
> address structure members to 8-bytes in all cases. This has no effect on
> 64-bit systems, but fixes the updated PMDs on 32-bit.
I agree to align on 64-bit in mbuf.
> Fixes: f4356d7ca168 ("net/i40e: eliminate mbuf write on rearm")
> Fixes: f160666a1073 ("net/ixgbe: eliminate mbuf write on rearm")
[...]
> --- a/lib/librte_eal/common/include/rte_memory.h
> +++ b/lib/librte_eal/common/include/rte_memory.h
> -typedef uint64_t phys_addr_t; /**< Physical address definition. */
> +/** Physical address definition. */
> +typedef uint64_t phys_addr_t __rte_aligned(sizeof(uint64_t));
Why setting this constraint for everyone?
next prev parent reply other threads:[~2017-04-28 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 8:15 [PATCH] eal: fix 64bit address alignment in 32-bit builds Bruce Richardson
2017-04-28 8:19 ` Bruce Richardson
2017-04-28 8:56 ` Thomas Monjalon [this message]
2017-04-28 9:03 ` Bruce Richardson
2017-04-28 9:21 ` Thomas Monjalon
2017-04-28 9:32 ` Bruce Richardson
2017-04-28 9:56 ` Olivier Matz
2017-04-28 10:14 ` Bruce Richardson
2017-04-28 13:10 ` [PATCH v2] mbuf: " Bruce Richardson
2017-04-30 19:40 ` Thomas Monjalon
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=1797441.atIi8ZZIaG@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.