DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Shijith Thotton <sthotton@marvell.com>, dev@dpdk.org
Subject: Re: [PATCH 1/2] event/cnxk: fix ns to ticks conversion
Date: Fri, 26 May 2023 16:01:17 +0530	[thread overview]
Message-ID: <CALBAE1M9L+i2mM1zHGH8AFgVF-JGxJ4+VH2zXkCS=gy3Ua0mFQ@mail.gmail.com> (raw)
In-Reply-To: <20230524085233.10003-1-pbhagavatula@marvell.com>

On Wed, May 24, 2023 at 2:22 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> The number of timeout ticks is dependent on the global dequeue
> timeout configured.
>
> Fixes: 6223ede20361 ("event/cnxk: add event port link and unlink")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

Series applied to dpdk-next-net-eventdev/for-main. Thanks


> ---
>  drivers/event/cnxk/cnxk_eventdev.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/event/cnxk/cnxk_eventdev.c b/drivers/event/cnxk/cnxk_eventdev.c
> index 99f9cdcd0d..3a05a59c75 100644
> --- a/drivers/event/cnxk/cnxk_eventdev.c
> +++ b/drivers/event/cnxk/cnxk_eventdev.c
> @@ -323,9 +323,9 @@ int
>  cnxk_sso_timeout_ticks(struct rte_eventdev *event_dev, uint64_t ns,
>                        uint64_t *tmo_ticks)
>  {
> -       RTE_SET_USED(event_dev);
> -       *tmo_ticks = NSEC2TICK(ns, rte_get_timer_hz());
> +       struct cnxk_sso_evdev *dev = cnxk_sso_pmd_priv(event_dev);
>
> +       *tmo_ticks = dev->deq_tmo_ns ? ns / dev->deq_tmo_ns : 0;
>         return 0;
>  }
>
> --
> 2.25.1
>

      parent reply	other threads:[~2023-05-26 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  8:52 pbhagavatula
2023-05-24  8:52 ` [PATCH 2/2] event/cnxk: honor event limit set by config pbhagavatula
2023-05-26 10:31 ` 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='CALBAE1M9L+i2mM1zHGH8AFgVF-JGxJ4+VH2zXkCS=gy3Ua0mFQ@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --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).