All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Gregory Etelson <getelson@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix representor interrupts handler assignment
Date: Tue, 27 Jul 2021 07:32:57 +0000	[thread overview]
Message-ID: <DM4PR12MB5054FB8029C8AA1F697EC5FCCFE99@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210720153819.32496-1-getelson@nvidia.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Gregory Etelson
> Sent: Tuesday, July 20, 2021 6:38 PM
> To: dev@dpdk.org
> Cc: Gregory Etelson <getelson@nvidia.com>; stable@dpdk.org; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>;
> Shahaf Shuler <shahafs@nvidia.com>
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix representor interrupts handler
> assignment
> 
> In mlx5 PMD the PCI device interrupt vector was used by Uplink representor
> exclusively and other VF representors did not support interrupt mode.
> All the VFs and Uplink representors are separate ethernet devices and must
> have dedicated interrupt vectors.
> The fix provides each representor with a dedicated interrupt vector.
> 
> Cc: stable@dpdk.org
> 
> Fixes: 5882bde88da2 ("net/mlx5: fix representor interrupts handler")
> 
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2021-07-27  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 15:38 [dpdk-dev] [PATCH] net/mlx5: fix representor interrupts handler assignment Gregory Etelson
2021-07-27  7:32 ` Raslan Darawsheh [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=DM4PR12MB5054FB8029C8AA1F697EC5FCCFE99@DM4PR12MB5054.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.