DPDK patches and discussions
 help / color / mirror / Atom feed
From: Harman Kalra <hkalra@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] interrupts: do not resize event list for non MSIX
Date: Fri, 29 Oct 2021 09:38:25 +0000	[thread overview]
Message-ID: <BN9PR18MB4204735791144CE216EB4E18C5879@BN9PR18MB4204.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20211029073819.29336-1-david.marchand@redhat.com>



> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, October 29, 2021 1:08 PM
> To: dev@dpdk.org
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>; Dmitry Kozlyuk
> <dmitry.kozliuk@gmail.com>; Harman Kalra <hkalra@marvell.com>
> Subject: [EXT] [PATCH] interrupts: do not resize event list for non MSIX
> 
> External Email
> 
> ----------------------------------------------------------------------
> Resizing event list only makes sense in MSIX case.
> 
> Besides, event list has always been RTE_MAX_RXTX_INTR_VEC_ID large.
> Let's restore this assumption for code that might rely on this property and
> only enlarge the event list when necessary.
> 
> Bugzilla ID: 843, 865
> Fixes: 8cb5d08db940 ("interrupts: extend event list")
> 

Thanks David for fixing this.

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

Thanks
Harman

> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  drivers/bus/pci/linux/pci_vfio.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/bus/pci/linux/pci_vfio.c b/drivers/bus/pci/linux/pci_vfio.c
> index f622e7f8e6..edcee92556 100644
> --- a/drivers/bus/pci/linux/pci_vfio.c
> +++ b/drivers/bus/pci/linux/pci_vfio.c
> @@ -266,12 +266,6 @@ pci_vfio_setup_interrupts(struct rte_pci_device
> *dev, int vfio_dev_fd)
>  			return -1;
>  		}
> 
> -		/* Reallocate the efds and elist fields of intr_handle based
> -		 * on PCI device MSIX size.
> -		 */
> -		if (rte_intr_event_list_update(dev->intr_handle, irq.count))
> -			return -1;
> -
>  		/* if this vector cannot be used with eventfd, fail if we
> explicitly
>  		 * specified interrupt type, otherwise continue */
>  		if ((irq.flags & VFIO_IRQ_INFO_EVENTFD) == 0) { @@ -283,6
> +277,14 @@ pci_vfio_setup_interrupts(struct rte_pci_device *dev, int
> vfio_dev_fd)
>  				continue;
>  		}
> 
> +		/* Reallocate the efds and elist fields of intr_handle based
> +		 * on PCI device MSIX size.
> +		 */
> +		if (i == VFIO_PCI_MSIX_IRQ_INDEX &&
> +				(uint32_t)rte_intr_nb_intr_get(dev-
> >intr_handle) < irq.count &&
> +				rte_intr_event_list_update(dev->intr_handle,
> irq.count))
> +			return -1;
> +
>  		/* set up an eventfd for interrupts */
>  		fd = eventfd(0, EFD_NONBLOCK | EFD_CLOEXEC);
>  		if (fd < 0) {
> --
> 2.23.0


  reply	other threads:[~2021-10-29  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  7:38 [dpdk-dev] " David Marchand
2021-10-29  9:38 ` Harman Kalra [this message]
2021-10-29 12:43   ` [dpdk-dev] [EXT] " David Marchand

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=BN9PR18MB4204735791144CE216EB4E18C5879@BN9PR18MB4204.namprd18.prod.outlook.com \
    --to=hkalra@marvell.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.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).