From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
Cc: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2] eventdev/eth_tx: fix queue add logic
Date: Mon, 14 Feb 2022 20:53:34 +0530 [thread overview]
Message-ID: <CALBAE1NbAU6icFx+Er4J_CBaMdsh5dXy7L9BT45wM9ezn5V-uw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB434878ED0F6FE448058979BFFD309@DM6PR11MB4348.namprd11.prod.outlook.com>
On Fri, Feb 11, 2022 at 10:03 PM Jayatheerthan, Jay
<jay.jayatheerthan@intel.com> wrote:
>
> Looks good. Thanks.
>
> Acked-by: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
>
> -Jay
>
>
>
> > -----Original Message-----
> > From: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
> > Sent: Wednesday, February 9, 2022 11:02 AM
> > To: Jayatheerthan, Jay <jay.jayatheerthan@intel.com>; jerinj@marvell.com
> > Cc: dev@dpdk.org
> > Subject: [PATCH v2] eventdev/eth_tx: fix queue add logic
> >
> > The internal function txa_service_queue_add is returning 0
> > in case of error. correct this logic to return a negative value
> > to indicate failure.
> >
> > Fixes: a3bbf2e09756 ("eventdev: add eth Tx adapter implementation")
> >
> > Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
> >
> > ---
> > v2:
> > * adjust commit message line size
> > ---
> > lib/eventdev/rte_event_eth_tx_adapter.c | 14 +++++++++-----
> > 1 file changed, 9 insertions(+), 5 deletions(-)
> >
> > diff --git a/lib/eventdev/rte_event_eth_tx_adapter.c b/lib/eventdev/rte_event_eth_tx_adapter.c
> > index c17f33f098..1b304f0a73 100644
> > --- a/lib/eventdev/rte_event_eth_tx_adapter.c
> > +++ b/lib/eventdev/rte_event_eth_tx_adapter.c
> > @@ -806,10 +806,8 @@ txa_service_queue_add(uint8_t id,
> >
> > rte_spinlock_lock(&txa->tx_lock);
> >
> > - if (txa_service_is_queue_added(txa, eth_dev, tx_queue_id)) {
> > - rte_spinlock_unlock(&txa->tx_lock);
> > - return 0;
> > - }
> > + if (txa_service_is_queue_added(txa, eth_dev, tx_queue_id))
> > + goto ret_unlock;
> >
> > ret = txa_service_queue_array_alloc(txa, eth_dev->data->port_id);
> > if (ret)
> > @@ -821,6 +819,8 @@ txa_service_queue_add(uint8_t id,
> >
> > tdi = &txa->txa_ethdev[eth_dev->data->port_id];
> > tqi = txa_service_queue(txa, eth_dev->data->port_id, tx_queue_id);
> > + if (tqi == NULL)
> > + goto err_unlock;
> >
> > txa_retry = &tqi->txa_retry;
> > txa_retry->id = txa->id;
> > @@ -836,6 +836,10 @@ txa_service_queue_add(uint8_t id,
> > tdi->nb_queues++;
> > txa->nb_queues++;
> >
> > +ret_unlock:
> > + rte_spinlock_unlock(&txa->tx_lock);
> > + return 0;
> > +
> > err_unlock:
> > if (txa->nb_queues == 0) {
> > txa_service_queue_array_free(txa,
> > @@ -844,7 +848,7 @@ txa_service_queue_add(uint8_t id,
> > }
> >
> > rte_spinlock_unlock(&txa->tx_lock);
> > - return 0;
> > + return -1;
> > }
> >
> > static int
> > --
> > 2.23.0
>
prev parent reply other threads:[~2022-02-14 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 5:23 [PATCH] " Naga Harish K S V
2022-02-09 5:31 ` [PATCH v2] " Naga Harish K S V
2022-02-11 16:33 ` Jayatheerthan, Jay
2022-02-14 15:23 ` Jerin Jacob [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=CALBAE1NbAU6icFx+Er4J_CBaMdsh5dXy7L9BT45wM9ezn5V-uw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=s.v.naga.harish.k@intel.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).