From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: "Jerin Jacob" <jerinj@marvell.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [EXTERNAL] [PATCH] eventdev: make flag types consistent with API
Date: Thu, 26 Jun 2025 16:36:23 +0200 [thread overview]
Message-ID: <32c86de3-5d1f-4e42-ae1d-19eccaac48e5@lysator.liu.se> (raw)
In-Reply-To: <BY3PR18MB478506E493537E8C47F2B21FC87AA@BY3PR18MB4785.namprd18.prod.outlook.com>
On 2025-06-26 16:12, Jerin Jacob wrote:
>> -----Original Message-----
>> From: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
>> Sent: Thursday, June 26, 2025 7:23 PM
>> To: Jerin Jacob <jerinj@marvell.com>
>> Cc: dev@dpdk.org; Mattias Rönnblom <hofors@lysator.liu.se>; Mattias
>> Rönnblom <mattias.ronnblom@ericsson.com>
>> Subject: [EXTERNAL] [PATCH] eventdev: make flag types consistent with API
>>
>> Make RTE_EVENT_DEV_CAP_* flags' type consistent with the
>> rte_event_dev_info. event_dev_cap's type. Make
>> RTE_EVENT_DEV_CFG_PER_DEQUEUE_TIMEOUT consistent with
>> rte_event_dev_config. event_dev_cfg. Make RTE_EVENT_QUEUE_CFG_*
>> consistent with rte_event_queue_conf. event_queue_cfg.
>> ZjQcmQRYFpfptBannerStart Prioritize security for external emails:
>> Confirm sender and content safety before clicking links or opening attachments
>> <https://us-phishalarm-
>> ewt.proofpoint.com/EWT/v1/CRVmXkqW!ts3Z1f8UAnUatM-
>> c2X0aD7H4_qqzjrySG1jUvYxf1eRBZ8860NkImwsi5uDUghDl9AKXmmrCtH3GlRgf
>> gCqT-4SjRdXOG8_TYEA-KJNabA$>
>> Report Suspicious
>>
>> ZjQcmQRYFpfptBannerEnd
>> Make RTE_EVENT_DEV_CAP_* flags' type consistent with the
>> rte_event_dev_info.event_dev_cap's type.
>>
>> Make RTE_EVENT_DEV_CFG_PER_DEQUEUE_TIMEOUT consistent with
>> rte_event_dev_config.event_dev_cfg.
>>
>> Make RTE_EVENT_QUEUE_CFG_* consistent with
>> rte_event_queue_conf.event_queue_cfg.
>>
>> Make RTE_EVENT_PORT_CFG_* consistent with
>> rte_event_port_conf.event_port_cfg.
>>
>> Make RTE_EVENT_TIMER_ADAPTER_CAP_* consistent with the caps parameter
>> in rte_event_eth_rx_adapter_caps_get().
>>
>> The flags were all unsigned long longs (64 bits), but the event_dev_cap,
>> event_dev_cfg, event_queue_cfg, and event_port_cfg fields and the caps
>> parameter are all uint32_t. This change makes the flags uint32_ts.
>>
>> Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
>> ---
>> lib/eventdev/rte_eventdev.h | 64 ++++++++++++++++++-------------------
>> 1 file changed, 32 insertions(+), 32 deletions(-)
>>
>> diff --git a/lib/eventdev/rte_eventdev.h b/lib/eventdev/rte_eventdev.h index
>> 3c7fcbf0be..9b44c24f0e 100644
>> --- a/lib/eventdev/rte_eventdev.h
>> +++ b/lib/eventdev/rte_eventdev.h
>> @@ -249,7 +249,7 @@ struct rte_mbuf; /* we just use mbuf pointers; no need
>> to include rte_mbuf.h */ struct rte_event;
>>
>> /* Event device capability bitmap flags */
>> -#define RTE_EVENT_DEV_CAP_QUEUE_QOS (1ULL << 0)
>> +#define RTE_EVENT_DEV_CAP_QUEUE_QOS (UINT32_C(1) << 0)
>
> Use RTE_BIT*
>
>
Of course. Thanks.
next prev parent reply other threads:[~2025-06-26 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 13:52 Mattias Rönnblom
2025-06-26 14:12 ` [EXTERNAL] " Jerin Jacob
2025-06-26 14:36 ` Mattias Rönnblom [this message]
2025-06-26 14:18 ` [PATCH v2] " Mattias Rönnblom
2025-06-27 6:46 ` [EXTERNAL] " 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=32c86de3-5d1f-4e42-ae1d-19eccaac48e5@lysator.liu.se \
--to=hofors@lysator.liu.se \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mattias.ronnblom@ericsson.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).