From: fengchengwen <fengchengwen@huawei.com>
To: <pbhagavatula@marvell.com>, <jerinj@marvell.com>,
Kevin Laatz <kevin.laatz@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2] dmadev: standardize alignment
Date: Sat, 10 Feb 2024 19:34:25 +0800 [thread overview]
Message-ID: <c62af716-50e7-b080-10be-d9353e092e2d@huawei.com> (raw)
In-Reply-To: <20240210062758.1510-1-pbhagavatula@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 2024/2/10 14:27, pbhagavatula@marvell.com wrote:
> From: Pavan Nikhilesh<pbhagavatula@marvell.com>
>
> Align fp_objects based on cacheline size defined
> by build configuration.
>
> Signed-off-by: Pavan Nikhilesh<pbhagavatula@marvell.com>
> ---
> v2 Changes:
> - Drop malloc changes.
>
> lib/dmadev/rte_dmadev_core.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/dmadev/rte_dmadev_core.h b/lib/dmadev/rte_dmadev_core.h
> index 064785686f..e8239c2d22 100644
> --- a/lib/dmadev/rte_dmadev_core.h
> +++ b/lib/dmadev/rte_dmadev_core.h
> @@ -73,7 +73,7 @@ struct rte_dma_fp_object {
> rte_dma_completed_t completed;
> rte_dma_completed_status_t completed_status;
> rte_dma_burst_capacity_t burst_capacity;
> -} __rte_aligned(128);
> +} __rte_cache_aligned;
>
> extern struct rte_dma_fp_object *rte_dma_fp_objs;
>
> --
> 2.25.1
>
[-- Attachment #2: Type: text/html, Size: 1646 bytes --]
next prev parent reply other threads:[~2024-02-10 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 9:06 [PATCH] dmadev: standardize alignment and allocation pbhagavatula
2024-02-04 1:38 ` fengchengwen
2024-02-10 6:20 ` [EXT] " Pavan Nikhilesh Bhagavatula
2024-02-10 6:27 ` [PATCH v2] dmadev: standardize alignment pbhagavatula
2024-02-10 11:34 ` fengchengwen [this message]
2024-02-19 1:32 ` 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=c62af716-50e7-b080-10be-d9353e092e2d@huawei.com \
--to=fengchengwen@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=pbhagavatula@marvell.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).