DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Luka Jankovic <luka.jankovic@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Jerin Jacob" <jerinj@marvell.com>,
	"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: RE: [EXTERNAL] [RFC PATCH v6 1/2] eventdev: add atomic queue to test-eventdev app
Date: Fri, 14 Feb 2025 15:59:33 +0000	[thread overview]
Message-ID: <PH0PR18MB4086E14E19F6767BD7D3B499DEFE2@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <8c8c0d1f2a82ff5097cd6dd0d8395c4a2741df66.camel@ericsson.com>

> On Tue, 2025-02-04 at 16:11 +0000, Pavan Nikhilesh Bhagavatula wrote:
> > > Add an atomic queue test to the test-eventdev app, which is based on the
> > > order queue test that exclusively uses atomic queues.
> > >
> > > This makes it compatible with event devices such as the
> > > distributed software eventdev.
> > >
> > > The test detects if port maintenance is required.
> > >
> > > To verify atomicity, a spinlock is used for each combination of queue and
> > > flow.
> > > It is acquired whenever an event is dequeued for processing and
> > > released when processing is finished.
> > >
> > > The test will fail if a port attempts to acquire a lock which is already
> > > held.
> > >
> > > Signed-off-by: Luka Jankovic <luka.jankovic@ericsson.com>
> >
> > It would be great if you could add atomic-atq test too.
> 
> I will add atomic-atq, but I only have access to sw and dsw, so I am unable to
> test it locally.

I will help you out with testing on CNXK which supports atq.

Thanks, 
Pavan.

  reply	other threads:[~2025-02-14 15:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 14:48 [RFC v2 1/1] " Luka Jankovic
2024-12-23 11:16 ` Mattias Rönnblom
2025-01-09 10:22   ` Luka Jankovic
2025-01-13  9:04 ` [RFC v3 " ejnulak
2025-01-13 12:17 ` [RFC v4 " Luka Jankovic
2025-01-13 12:27   ` [EXTERNAL] " Jerin Jacob
2025-01-15 13:38   ` [RFC v5 1/2] " Luka Jankovic
2025-01-22 10:20     ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-01-22 15:10       ` Luka Jankovic
2025-01-24  9:59     ` [RFC PATCH v6 " Luka Jankovic
2025-02-04 16:11       ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-02-14  9:58         ` Luka Jankovic
2025-02-14 15:59           ` Pavan Nikhilesh Bhagavatula [this message]
2025-02-19 13:43       ` [RFC v7 0/4] eventdev: atomic tests " Luka Jankovic
2025-02-19 13:43         ` [RFC v7 1/4] eventdev: atomic common for " Luka Jankovic
2025-02-19 13:43         ` [RFC v7 2/4] eventdev: add atomic queue test to test-evnetdev app Luka Jankovic
2025-02-19 13:43         ` [RFC v7 3/4] eventdev: add atomic atq to test-eventdev app Luka Jankovic
2025-02-19 13:43         ` [RFC v7 4/4] eventdev: documentation for atomic queue and atomic atq tests Luka Jankovic
2025-02-20  9:13         ` [EXTERNAL] [RFC v7 0/4] eventdev: atomic tests to test-eventdev app Pavan Nikhilesh Bhagavatula
2025-01-24  9:59     ` [RFC PATCH v6 2/2] eventdev: documentation for atomic queue test Luka Jankovic
2025-01-15 13:38   ` [RFC v5 " Luka Jankovic

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=PH0PR18MB4086E14E19F6767BD7D3B499DEFE2@PH0PR18MB4086.namprd18.prod.outlook.com \
    --to=pbhagavatula@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=luka.jankovic@ericsson.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).