From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matan Azrad <matan@mellanox.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 2/2] net/mlx5: support device removal event
Date: Fri, 8 Sep 2017 11:05:24 +0100 [thread overview]
Message-ID: <1749576e-c112-c773-e891-b11f91be7fe3@intel.com> (raw)
In-Reply-To: <1504710238-25726-2-git-send-email-matan@mellanox.com>
On 9/6/2017 4:03 PM, Matan Azrad wrote:
> Extend the LSC event handling to support the device removal as well.
>
> The mlx5 event handling has been made capable of receiving and
> signaling several event types at once.
>
> This support includes next:
> 1. Removal event detection according to the user configuration.
> 2. Calling to all registered mlx5 removal callbacks.
> 3. Capabilities extension to include removal interrupt handling.
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
Hi Matan,
Can you please update features file [1] to document the support [2] ?
[1]
doc/guides/nics/features/mlx5.ini
[2]
"Removal event ="
next prev parent reply other threads:[~2017-09-08 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 15:03 [dpdk-dev] [PATCH v4 1/2] net/mlx5: link status update separation Matan Azrad
2017-09-06 15:03 ` [dpdk-dev] [PATCH v4 2/2] net/mlx5: support device removal event Matan Azrad
2017-09-06 15:14 ` Adrien Mazarguil
2017-09-08 10:05 ` Ferruh Yigit [this message]
2017-09-08 10:47 ` [dpdk-dev] [PATCH v5] " Matan Azrad
2017-09-11 16:12 ` Ferruh Yigit
2017-09-06 15:14 ` [dpdk-dev] [PATCH v4 1/2] net/mlx5: link status update separation Adrien Mazarguil
2017-09-11 16:12 ` 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=1749576e-c112-c773-e891-b11f91be7fe3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=nelio.laranjeiro@6wind.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).