From: Shahaf Shuler <shahafs@mellanox.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Yongseok Koh <yskoh@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix link status initialization
Date: Wed, 11 Apr 2018 09:05:49 +0000 [thread overview]
Message-ID: <DB7PR05MB44267C68575754C3F0FDA452C3BD0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180410081754.byft4mcgqa7wbmvx@laranjeiro-vm.dev.6wind.com>
Tuesday, April 10, 2018 11:18 AM, Nélio Laranjeiro:
> Subject: Re: [PATCH v2] net/mlx5: fix link status initialization
>
> On Tue, Apr 10, 2018 at 09:13:36AM +0300, Shahaf Shuler wrote:
> > Following commit 7ba5320baa32 ("net/mlx5: fix link status behavior")
> > The initial link status is no longer set as part of the port start.
> >
> > When LSC interrupts are enabled, ethdev layer reads the link status
> > directly from the device data instead of using the PMD callback.
> > This may cause application to query the link as down while in fact it
> > was already up before the DPDK application start (and no interrupt to
> > fix it).
> >
> > Fixes: 7ba5320baa32 ("net/mlx5: fix link status behavior")
> > Cc: nelio.laranjeiro@6wind.com
> >
> > Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> > Acked-by: Yongseok Koh <yskoh@mellanox.com>
> > ---
> >
> > On v2:
> > - Reworded commit log.
> > - Cleared the wait_to_complete on the link update call.
> >
> > ---
> > drivers/net/mlx5/mlx5.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c index
> > cfab558979..3d222df707 100644
> > --- a/drivers/net/mlx5/mlx5.c
> > +++ b/drivers/net/mlx5/mlx5.c
> > @@ -991,6 +991,12 @@ mlx5_pci_probe(struct rte_pci_driver *pci_drv
> __rte_unused,
> > DRV_LOG(DEBUG, "port %u forcing Ethernet interface up",
> > eth_dev->data->port_id);
> > mlx5_set_link_up(eth_dev);
> > + /*
> > + * Even though the interrupt handler is not installed yet,
> > + * interrupts will still trigger on the asyn_fd from
> > + * Verbs context returned by ibv_open_device().
> > + */
> > + mlx5_link_update(eth_dev, 0);
> > /* Store device configuration on private structure. */
> > priv->config = config;
> > continue;
> > --
> > 2.12.0
>
> You should have linked this patch with the ethdev one[1], if the ethdev is
> refused, this patch won't solve anything.
>
> With a reserves of acceptance of [1]:
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
As the ethdev pathc applied -> Applied to next-net-mlx, thanks
prev parent reply other threads:[~2018-04-11 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 4:48 [dpdk-dev] [PATCH] " Shahaf Shuler
2018-04-04 7:30 ` Nélio Laranjeiro
2018-04-04 9:58 ` Shahaf Shuler
2018-04-04 12:10 ` Nélio Laranjeiro
2018-04-05 5:35 ` Shahaf Shuler
2018-04-05 6:51 ` Nélio Laranjeiro
2018-04-08 13:09 ` Shahaf Shuler
2018-04-09 8:27 ` Nélio Laranjeiro
2018-04-09 12:28 ` Shahaf Shuler
2018-04-09 13:26 ` Nélio Laranjeiro
2018-04-09 14:07 ` Nélio Laranjeiro
2018-04-10 6:13 ` [dpdk-dev] [PATCH v2] " Shahaf Shuler
2018-04-10 8:17 ` Nélio Laranjeiro
2018-04-11 9:05 ` Shahaf Shuler [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=DB7PR05MB44267C68575754C3F0FDA452C3BD0@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=yskoh@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).