From: Yongseok Koh <yskoh@mellanox.com>
To: "Player, Timmons" <Timmons.Player@spirent.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/igb: fix LSC interrupt when using MSI-X
Date: Wed, 27 Mar 2019 18:34:43 +0000 [thread overview]
Message-ID: <85FB2DBD-5692-4F4A-BDD5-926A04542BA1@mellanox.com> (raw)
In-Reply-To: <20190315190854.4486-1-timmons.player@spirent.com>
> On Mar 15, 2019, at 12:09 PM, Player, Timmons <Timmons.Player@spirent.com> wrote:
>
> [ backported from upstream commit 7f5c81d5689d4d1b4dce8279a6eb3318bddf1607 ]
>
> Take the 'other interrupt' into account when setting up
> MSI-X interrupts and use the proper mask when enabling it.
> Also, rearm the MSI-X vector after the LSC interrupt fires.
>
> This change allows both LSC and RXQ interrupts to work at
> the same time when using MSI-X interrupts.
>
> Signed-off-by: Timmons C. Player <timmons.player@spirent.com>
> ---
applied to stable/17.11
Thanks,
Yongseok
prev parent reply other threads:[~2019-03-27 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 19:09 Player, Timmons
2019-03-27 18:34 ` Yongseok Koh [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=85FB2DBD-5692-4F4A-BDD5-926A04542BA1@mellanox.com \
--to=yskoh@mellanox.com \
--cc=Timmons.Player@spirent.com \
--cc=stable@dpdk.org \
/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).