patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Shijith Thotton <sthotton@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: Shijith Thotton <sthotton@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: RE: [PATCH] examples/l2fwd-event: fix function args of worker cleanup
Date: Tue, 13 Dec 2022 15:13:43 +0000	[thread overview]
Message-ID: <PH0PR18MB4086BD72C7F988000C594CDDDEE39@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <fdc89e404bfe8e67144fb2ca1073e029e0a44200.1670859887.git.sthotton@marvell.com>



> -----Original Message-----
> From: Shijith Thotton <sthotton@marvell.com>
> Sent: Monday, December 12, 2022 9:19 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: Shijith Thotton <sthotton@marvell.com>; dev@dpdk.org; Pavan
> Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> Subject: [PATCH] examples/l2fwd-event: fix function args of worker cleanup
> 
> Fixed function call arguments of l2fwd worker cleanup. Number of events
> enqueued and dequeued are set the opposite.
> 
> Fixes: 622ebb6b4a7d ("examples/l2fwd-event: clean up worker state before
> exit")
Cc: stable@dpdk.org
> 
> Signed-off-by: Shijith Thotton <sthotton@marvell.com>
Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
>  examples/l2fwd-event/l2fwd_event.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/examples/l2fwd-event/l2fwd_event.c b/examples/l2fwd-
> event/l2fwd_event.c
> index 63450537fe..4b5a032e35 100644
> --- a/examples/l2fwd-event/l2fwd_event.c
> +++ b/examples/l2fwd-event/l2fwd_event.c
> @@ -284,7 +284,7 @@ l2fwd_event_loop_burst(struct l2fwd_resources
> *rsrc,
>  		}
>  	}
> 
> -	l2fwd_event_worker_cleanup(event_d_id, port_id, ev, nb_rx,
> nb_tx, 0);
> +	l2fwd_event_worker_cleanup(event_d_id, port_id, ev, nb_tx,
> nb_rx, 0);
>  }
> 
>  static __rte_always_inline void
> @@ -468,7 +468,7 @@ l2fwd_event_loop_vector(struct l2fwd_resources
> *rsrc, const uint32_t flags)
>  		}
>  	}
> 
> -	l2fwd_event_worker_cleanup(event_d_id, port_id, ev, nb_rx,
> nb_tx, 1);
> +	l2fwd_event_worker_cleanup(event_d_id, port_id, ev, nb_tx,
> nb_rx, 1);
>  }
> 
>  static void __rte_noinline
> --
> 2.25.1


       reply	other threads:[~2022-12-13 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fdc89e404bfe8e67144fb2ca1073e029e0a44200.1670859887.git.sthotton@marvell.com>
2022-12-13 15:13 ` Pavan Nikhilesh Bhagavatula [this message]
2023-01-18 10:30   ` 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=PH0PR18MB4086BD72C7F988000C594CDDDEE39@PH0PR18MB4086.namprd18.prod.outlook.com \
    --to=pbhagavatula@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    --cc=sthotton@marvell.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).