DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Huichao Cai" <chcchc88@163.com>
To: "Jerin Jacob" <jerinj@marvell.com>
Cc: "Kiran Kumar Kokkilagadda" <kirankumark@marvell.com>,
	 "Nithin Kumar Dabilpuram" <ndabilpuram@marvell.com>,
	 "yanzhirun_163@163.com" <yanzhirun_163@163.com>,
	 "david.marchand@redhat.com" <david.marchand@redhat.com>,
	 "dev@dpdk.org" <dev@dpdk.org>
Subject: Re:RE: [EXTERNAL] [PATCH v4 2/2] graph: add alignment to the member of rte_node
Date: Thu, 14 Nov 2024 20:06:51 +0800 (CST)	[thread overview]
Message-ID: <470e043d.ab5e.1932a91b2f3.Coremail.chcchc88@163.com> (raw)
In-Reply-To: <BY3PR18MB4785ED6DAA3C4BF4FD350108C85B2@BY3PR18MB4785.namprd18.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

Hi, Jerin. Like this?




diff --git a/lib/graph/rte_graph_worker_common.h b/lib/graph/rte_graph_worker_common.h

index a518af2b2a..f9ff7dd8c9 100644

--- a/lib/graph/rte_graph_worker_common.h

+++ b/lib/graph/rte_graph_worker_common.h

@@ -104,15 +104,19 @@ struct __rte_cache_aligned rte_node {

        /** Original process function when pcap is enabled. */

        rte_node_process_t original_process;

 

+       /** Fast schedule area for mcore dispatch model. */

        union {

-               /* Fast schedule area for mcore dispatch model */

-               struct {

+               alignas(RTE_CACHE_LINE_MIN_SIZE) struct {

                        unsigned int lcore_id;  /**< Node running lcore. */

                        uint64_t total_sched_objs; /**< Number of objects scheduled. */

                        uint64_t total_sched_fail; /**< Number of scheduled failure. */

                } dispatch;

        };

+

+       /** Fast path area cache line 1. */

+       alignas(RTE_CACHE_LINE_MIN_SIZE)

        rte_graph_off_t xstat_off; /**< Offset to xstat counters. */

+

        /* Fast path area  */

        __extension__ struct __rte_cache_aligned {

 #define RTE_NODE_CTX_SZ 16



[-- Attachment #2: Type: text/html, Size: 2621 bytes --]

  reply	other threads:[~2024-11-14 12:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  8:04 [PATCH] graph: optimize graph search when scheduling nodes Huichao cai
2024-11-07  9:37 ` [EXTERNAL] " Jerin Jacob
2024-11-08  1:39   ` Huichao Cai
2024-11-08 12:22     ` Jerin Jacob
2024-11-08 13:38       ` David Marchand
2024-11-11  5:38         ` Jerin Jacob
2024-11-12  8:51           ` David Marchand
2024-11-12  9:35             ` Jerin Jacob
2024-11-12 12:57               ` Huichao Cai
2024-11-13  9:22               ` Huichao Cai
2024-11-14  7:09                 ` Jerin Jacob
2024-11-11  4:03 ` [PATCH v2] graph: mcore: optimize graph search Huichao Cai
2024-11-11  5:46   ` [EXTERNAL] " Jerin Jacob
2024-11-13  9:19     ` Huichao Cai
2024-11-13  7:35   ` [PATCH v3 1/2] " Huichao Cai
2024-11-13  7:35     ` [PATCH v3 2/2] graph: add alignment to the member of rte_node Huichao Cai
2024-11-14  7:14       ` [EXTERNAL] " Jerin Jacob
2024-11-14  8:45     ` [PATCH v4 1/2] graph: mcore: optimize graph search Huichao Cai
2024-11-14  8:45       ` [PATCH v4 2/2] graph: add alignment to the member of rte_node Huichao Cai
2024-11-14 10:05         ` [EXTERNAL] " Jerin Jacob
2024-11-14 12:06           ` Huichao Cai [this message]
2024-11-14 13:04             ` 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=470e043d.ab5e.1932a91b2f3.Coremail.chcchc88@163.com \
    --to=chcchc88@163.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=yanzhirun_163@163.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).