From: Luka Jankovic <luka.jankovic@ericsson.com>
To: "hofors@lysator.liu.se" <hofors@lysator.liu.se>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: Re: [RFC v2 1/1] eventdev: add atomic queue to test-eventdev app
Date: Thu, 9 Jan 2025 10:22:05 +0000 [thread overview]
Message-ID: <2a8225b89482530a305cb06ac63c858516ec663f.camel@ericsson.com> (raw)
In-Reply-To: <60865a29-7705-492f-9f5b-d5662b813a07@lysator.liu.se>
On Mon, 2024-12-23 at 12:16 +0100, Mattias Rönnblom wrote:
>
> > +static __rte_always_inline void
>
> Why is this __rte_always_inline?
>
The stage functions are based on the ones defined in test_order_queue.c and the
test_order_common.h respectively, where they were defined with
__rte_always_inline. I tried using normal inline and it works, so I will change
it.
Thank you for the feedback. I will revise and send a new version.
>
prev parent reply other threads:[~2025-01-09 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 14:48 Luka Jankovic
2024-12-23 11:16 ` Mattias Rönnblom
2025-01-09 10:22 ` Luka Jankovic [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=2a8225b89482530a305cb06ac63c858516ec663f.camel@ericsson.com \
--to=luka.jankovic@ericsson.com \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--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).