From: Shahaf Shuler <shahafs@mellanox.com>
To: Ophir Munk <ophirmu@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
Yongseok Koh <yskoh@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>, Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/3] net/mlx5: allow multiple probing for representor
Date: Wed, 24 Oct 2018 13:19:04 +0000 [thread overview]
Message-ID: <DB7PR05MB44268756E1631E7EB07B5046C3F60@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1540319157-11191-1-git-send-email-ophirmu@mellanox.com>
Tuesday, October 23, 2018 9:26 PM, Ophir Munk:
> Subject: [PATCH v4 1/3] net/mlx5: allow multiple probing for representor
>
> Implement probing of a rte device multiple times, see [1].
> Set PCI driver RTE_PCI_DRV_PROBE_AGAIN flag to enable multiple probing
> of the PCI device by the PCI common driver.
> Consecutive probing requests with a devargs string may contain repetitive
> master and representors devices for which eth device should be created only
> once. In case an eth device already exists - silently ignore it.
>
> [1]
> commit e9d159c3d534 ("eal: allow probing a device again")
>
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
Series applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-10-24 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 8:01 [dpdk-dev] [PATCH] net/mlx5: allow multi probing Ophir Munk
2018-10-05 1:41 ` Yongseok Koh
2018-10-05 11:20 ` Ophir Munk
2018-10-05 11:06 ` [dpdk-dev] [PATCH v2] net/mlx5: allow multiple probing for representor Ophir Munk
2018-10-05 18:06 ` Yongseok Koh
2018-10-09 22:23 ` Ophir Munk
2018-10-19 8:12 ` [dpdk-dev] [PATCH v3] " Ophir Munk
2018-10-23 18:26 ` [dpdk-dev] [PATCH v4 1/3] " Ophir Munk
2018-10-23 18:26 ` [dpdk-dev] [PATCH v4 2/3] net/mlx5: release port on close Ophir Munk
2018-10-23 18:26 ` [dpdk-dev] [PATCH v4 3/3] net/mlx5: close all ports on remove Ophir Munk
2018-10-24 13:19 ` 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=DB7PR05MB44268756E1631E7EB07B5046C3F60@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=thomas@monjalon.net \
--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).