DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Matan Azrad <matan@mellanox.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1 0/3] net/mlx4: additional interrupt handling fixes
Date: Tue, 5 Sep 2017 15:28:01 +0200	[thread overview]
Message-ID: <20170905132801.GG21444@bidouze.vm.6wind.com> (raw)
In-Reply-To: <cover.1504614801.git.adrien.mazarguil@6wind.com>

On Tue, Sep 05, 2017 at 02:56:36PM +0200, Adrien Mazarguil wrote:
> While the previous interrupt rework improved the situation, it failed to
> address one last issue pointed out by Matan: RMV/LSC events may be missed
> and not reported to the application.
> 
> Adrien Mazarguil (3):
>   net/mlx4: fix unhandled event debug message
>   net/mlx4: fix rescheduled link status check
>   net/mlx4: merge interrupt collector function
> 
>  drivers/net/mlx4/mlx4_intr.c | 150 ++++++++++++++++++--------------------
>  1 file changed, 71 insertions(+), 79 deletions(-)
> 
> -- 
> 2.1.4
> 

For the series:

Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>

-- 
Gaëtan Rivet
6WIND

  parent reply	other threads:[~2017-09-05 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 12:56 Adrien Mazarguil
2017-09-05 12:56 ` [dpdk-dev] [PATCH v1 1/3] net/mlx4: fix unhandled event debug message Adrien Mazarguil
2017-09-05 12:56 ` [dpdk-dev] [PATCH v1 2/3] net/mlx4: fix rescheduled link status check Adrien Mazarguil
2017-09-05 12:56 ` [dpdk-dev] [PATCH v1 3/3] net/mlx4: merge interrupt collector function Adrien Mazarguil
2017-09-05 13:29   ` Gaëtan Rivet
2017-09-05 13:28 ` Gaëtan Rivet [this message]
2017-09-08  9:10 ` [dpdk-dev] [PATCH v1 0/3] net/mlx4: additional interrupt handling fixes Ferruh Yigit

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=20170905132801.GG21444@bidouze.vm.6wind.com \
    --to=gaetan.rivet@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.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).