From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Matan Azrad <matan@mellanox.com>
Cc: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
Subject: Re: [PATCH v4 1/2] net/mlx5: link status update separation
Date: Wed, 6 Sep 2017 17:14:14 +0200 [thread overview]
Message-ID: <20170906151414.GY4301@6wind.com> (raw)
In-Reply-To: <1504710238-25726-1-git-send-email-matan@mellanox.com>
On Wed, Sep 06, 2017 at 06:03:57PM +0300, Matan Azrad wrote:
> Link status is sometimes inconsistent during a LSC event.
> When it occurs, the PMD refrains from immediately notifying
> the application; instead, an alarm is scheduled to check
> link status later and notify the application once it has settled.
>
> In the previous code the alarm callback calls to the interrupt
> handler for link status recheck and may cause to unnecessary
> interrupt events check.
>
> This patch separates the link status update and the interrupt event
> handler to avoid the unnecessary check and arranges the interrupt
> handler for more interrupt supports in the future.
>
> Comment was added in the new function to explain the inconsistent
> link status reason.
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2017-09-06 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 15:03 [PATCH v4 1/2] net/mlx5: link status update separation Matan Azrad
2017-09-06 15:03 ` [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
2017-09-08 10:47 ` [PATCH v5] " Matan Azrad
2017-09-11 16:12 ` Ferruh Yigit
2017-09-06 15:14 ` Adrien Mazarguil [this message]
2017-09-11 16:12 ` [PATCH v4 1/2] net/mlx5: link status update separation 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=20170906151414.GY4301@6wind.com \
--to=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 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.