DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
	Heng Wang <heng.wang@ericsson.com>
Subject: Re: [dpdk-dev] [PATCH] event/dsw: flag proper eventdev adapter capabilities
Date: Wed, 30 Jun 2021 20:52:16 +0530	[thread overview]
Message-ID: <CALBAE1P3xLmA-shV1X5gVWxNhv6Gscr575nQJd365WkMkr7_hw@mail.gmail.com> (raw)
In-Reply-To: <20210614102358.11488-1-mattias.ronnblom@ericsson.com>

On Mon, Jun 14, 2021 at 3:54 PM Mattias Rönnblom
<mattias.ronnblom@ericsson.com> wrote:
>
> Set the appropriate capability flags for the RX, crypto and timer
> eventdev adapters to use.
>
> Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> Tested-by: Heng Wang <heng.wang@ericsson.com>

Applied to dpdk-next-net-eventdev/for-main. Thanks


> ---
>  drivers/event/dsw/dsw_evdev.c | 31 +++++++++++++++++++++++++++++++
>  1 file changed, 31 insertions(+)
>
> diff --git a/drivers/event/dsw/dsw_evdev.c b/drivers/event/dsw/dsw_evdev.c
> index 320a3784c..2301a4b7a 100644
> --- a/drivers/event/dsw/dsw_evdev.c
> +++ b/drivers/event/dsw/dsw_evdev.c
> @@ -370,6 +370,34 @@ dsw_close(struct rte_eventdev *dev)
>         return 0;
>  }
>
> +static int
> +dsw_eth_rx_adapter_caps_get(const struct rte_eventdev *dev __rte_unused,
> +                           const struct rte_eth_dev *eth_dev __rte_unused,
> +                           uint32_t *caps)
> +{
> +       *caps = RTE_EVENT_ETH_RX_ADAPTER_SW_CAP;
> +       return 0;
> +}
> +
> +static int
> +dsw_timer_adapter_caps_get(const struct rte_eventdev *dev __rte_unused,
> +                          uint64_t flags  __rte_unused, uint32_t *caps,
> +                          const struct rte_event_timer_adapter_ops **ops)
> +{
> +       *caps = 0;
> +       *ops = NULL;
> +       return 0;
> +}
> +
> +static int
> +dsw_crypto_adapter_caps_get(const struct rte_eventdev *dev  __rte_unused,
> +                           const struct rte_cryptodev *cdev  __rte_unused,
> +                           uint32_t *caps)
> +{
> +       *caps = RTE_EVENT_CRYPTO_ADAPTER_SW_CAP;
> +       return 0;
> +}
> +
>  static struct rte_eventdev_ops dsw_evdev_ops = {
>         .port_setup = dsw_port_setup,
>         .port_def_conf = dsw_port_def_conf,
> @@ -384,6 +412,9 @@ static struct rte_eventdev_ops dsw_evdev_ops = {
>         .dev_start = dsw_start,
>         .dev_stop = dsw_stop,
>         .dev_close = dsw_close,
> +       .eth_rx_adapter_caps_get = dsw_eth_rx_adapter_caps_get,
> +       .timer_adapter_caps_get = dsw_timer_adapter_caps_get,
> +       .crypto_adapter_caps_get = dsw_crypto_adapter_caps_get,
>         .xstats_get = dsw_xstats_get,
>         .xstats_get_names = dsw_xstats_get_names,
>         .xstats_get_by_name = dsw_xstats_get_by_name
> --
> 2.25.1
>

      reply	other threads:[~2021-06-30 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 10:23 Mattias Rönnblom
2021-06-30 15:22 ` 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=CALBAE1P3xLmA-shV1X5gVWxNhv6Gscr575nQJd365WkMkr7_hw@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=heng.wang@ericsson.com \
    --cc=jerinj@marvell.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).