DPDK patches and discussions
 help / color / mirror / Atom feed
From: Harman Kalra <hkalra@marvell.com>
To: Vladimir Ratnikov <vratnikov@netgate.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH] eal/interrupts: Allow UIO interrupts when using igb_uio
Date: Mon, 3 Jul 2023 07:19:31 +0000	[thread overview]
Message-ID: <BN9PR18MB42046836E6B0B1ECEB71877FC529A@BN9PR18MB4204.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230614134018.2344-1-vratnikov@netgate.com>


>  Some drivers and devices(ex: igc + i225/i226) use RTE_INTR_HANDLE_UIO
> handler when captured under igb_uio so just let them use it.
> 
> Signed-off-by: Vladimir Ratnikov <vratnikov@netgate.com>


Reviewed-by: Harman Kalra <hkalra@marvell.com>

Thanks
Harman 

> ---
>  lib/eal/linux/eal_interrupts.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/lib/eal/linux/eal_interrupts.c b/lib/eal/linux/eal_interrupts.c
> index c9881143be..037db09cfd 100644
> --- a/lib/eal/linux/eal_interrupts.c
> +++ b/lib/eal/linux/eal_interrupts.c
> @@ -1596,6 +1596,9 @@ rte_intr_cap_multiple(struct rte_intr_handle
> *intr_handle)
>  	if (rte_intr_type_get(intr_handle) == RTE_INTR_HANDLE_VDEV)
>  		return 1;
> 
> +	if (rte_intr_type_get(intr_handle) == RTE_INTR_HANDLE_UIO)
> +		return 1;
> +
>  	return 0;
>  }
> 
> --
> 2.34.1


      parent reply	other threads:[~2023-07-03  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 13:40 Vladimir Ratnikov
2023-06-14 16:46 ` Stephen Hemminger
2023-07-03 15:32   ` Thomas Monjalon
2023-07-04 10:45     ` Vladimir Ratnikov
2023-07-04 15:55       ` Stephen Hemminger
2023-07-04 18:19         ` Vladimir Ratnikov
2023-07-05 23:27           ` Stephen Hemminger
2023-10-31 17:17           ` Stephen Hemminger
2023-07-03  7:19 ` Harman Kalra [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=BN9PR18MB42046836E6B0B1ECEB71877FC529A@BN9PR18MB4204.namprd18.prod.outlook.com \
    --to=hkalra@marvell.com \
    --cc=dev@dpdk.org \
    --cc=vratnikov@netgate.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).