From: Yunsheng Lin <linyunsheng@huawei.com>
To: <longli@microsoft.com>, "K. Y. Srinivasan" <kys@microsoft.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
<edumazet@google.com>, <shiraz.saleem@intel.com>,
"Ajay Sharma" <sharmaajay@microsoft.com>
Cc: <linux-hyperv@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>
Subject: Re: [Patch v7 01/12] net: mana: Add support for auxiliary device
Date: Wed, 19 Oct 2022 11:29:54 +0800 [thread overview]
Message-ID: <8f23732f-8ee7-b120-1866-286503418d3e@huawei.com> (raw)
In-Reply-To: <1666034441-15424-2-git-send-email-longli@linuxonhyperv.com>
On 2022/10/18 3:20, longli@linuxonhyperv.com wrote:
> From: Long Li <longli@microsoft.com>
>
> In preparation for supporting MANA RDMA driver, add support for auxiliary
> device in the Ethernet driver. The RDMA device is modeled as an auxiliary
> device to the Ethernet device.
If the RDMA device is a auxiliary device in the Ethernet driver, is there
some type of hw reset that affect both net_device and ib_device?
Is there some kind of handling like pcie hot plug/unplug which already
handles this case, so the reset handling is not needed in the RDMA and
Ethernet driver?
>
> Reviewed-by: Dexuan Cui <decui@microsoft.com>
> Signed-off-by: Long Li <longli@microsoft.com>
> Acked-by: Haiyang Zhang <haiyangz@microsoft.com>
> ---
> Change log:
> v3: define mana_adev_idx_alloc and mana_adev_idx_free as static
> v7: fix a bug that may assign a negative value to adev->id
>
> drivers/net/ethernet/microsoft/Kconfig | 1 +
> drivers/net/ethernet/microsoft/mana/gdma.h | 2 +
> .../ethernet/microsoft/mana/mana_auxiliary.h | 10 +++
> drivers/net/ethernet/microsoft/mana/mana_en.c | 83 ++++++++++++++++++-
next prev parent reply other threads:[~2022-10-19 3:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 19:20 [Patch v7 00/12] Introduce Microsoft Azure Network Adapter (MANA) RDMA driver longli
2022-10-17 19:20 ` [Patch v7 01/12] net: mana: Add support for auxiliary device longli
2022-10-19 3:29 ` Yunsheng Lin [this message]
2022-10-19 19:51 ` Long Li
2022-10-17 19:20 ` [Patch v7 02/12] net: mana: Record the physical address for doorbell page region longli
2022-10-17 19:20 ` [Patch v7 03/12] net: mana: Handle vport sharing between devices longli
2022-10-17 19:20 ` [Patch v7 04/12] net: mana: Set the DMA device max segment size longli
2022-10-17 19:20 ` [Patch v7 05/12] net: mana: Export Work Queue functions for use by RDMA driver longli
2022-10-17 19:20 ` [Patch v7 06/12] net: mana: Record port number in netdev longli
2022-10-17 19:20 ` [Patch v7 07/12] net: mana: Move header files to a common location longli
2022-10-17 19:20 ` [Patch v7 08/12] net: mana: Define max values for SGL entries longli
2022-10-17 19:20 ` [Patch v7 09/12] net: mana: Define and process GDMA response code GDMA_STATUS_MORE_ENTRIES longli
2022-10-17 19:20 ` [Patch v7 10/12] net: mana: Define data structures for allocating doorbell page from GDMA longli
2022-10-19 0:32 ` Yunsheng Lin
2022-10-19 18:16 ` Long Li
2022-10-17 19:20 ` [Patch v7 11/12] net: mana: Define data structures for protection domain and memory registration longli
2022-10-17 19:20 ` [Patch v7 12/12] RDMA/mana_ib: Add a driver for Microsoft Azure Network Adapter longli
2022-10-18 10:11 ` Paolo Abeni
2022-10-19 18:35 ` Long Li
2022-10-19 1:17 ` Yunsheng Lin
2022-10-19 19:36 ` Long Li
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=8f23732f-8ee7-b120-1866-286503418d3e@huawei.com \
--to=linyunsheng@huawei.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharmaajay@microsoft.com \
--cc=shiraz.saleem@intel.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
/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
all inboxes | Powered by JetHome®