From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@xilinx.com>, Long Li <longli@microsoft.com>
Cc: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Ajay Sharma <sharmaajay@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [Patch v4 01/17] net/mana: add basic driver, build environment and doc
Date: Mon, 29 Aug 2022 09:58:03 +0200 [thread overview]
Message-ID: <1857175.eGJsNajkDb@thomas> (raw)
In-Reply-To: <PH7PR21MB3263FA65B7ED98E65F791CE4CE719@PH7PR21MB3263.namprd21.prod.outlook.com>
22/08/2022 20:27, Long Li:
> > Subject: Re: [Patch v4 01/17] net/mana: add basic driver, build environment
> > and doc
> >
> > On 8/22/2022 4:03 PM, Ferruh Yigit wrote:
> > >> + struct rte_pci_device *pci_dev,
> > >> + struct rte_ether_addr *mac_addr) {
> > >> + struct ibv_device **ibv_list;
> > >> + int ibv_idx;
> > >> + struct ibv_context *ctx;
> > >> + struct ibv_device_attr_ex dev_attr;
> > >> + int num_devices;
> > >> + int ret = 0;
> > >> + uint8_t port;
> > >> + struct mana_priv *priv = NULL;
> > >> + struct rte_eth_dev *eth_dev = NULL;
> > >> + bool found_port;
> > >> +
> > >> + ibv_list = ibv_get_device_list(&num_devices);
> > >> + for (ibv_idx = 0; ibv_idx < num_devices; ibv_idx++) {
> > >> + struct ibv_device *ibdev = ibv_list[ibv_idx];
> > >> + struct rte_pci_addr pci_addr;
> > >> +
> > >> + DRV_LOG(INFO, "Probe device name %s dev_name %s
> > >> ibdev_path %s",
> > >> + ibdev->name, ibdev->dev_name,
> > >> +ibdev->ibdev_path);
> > >> +
> > >> + if (mana_ibv_device_to_pci_addr(ibdev, &pci_addr))
> > >> + continue;
> > >> +
> > >> + /* Ignore if this IB device is not this PCI device */
> > >> + if (pci_dev->addr.domain != pci_addr.domain ||
> > >> + pci_dev->addr.bus != pci_addr.bus ||
> > >> + pci_dev->addr.devid != pci_addr.devid ||
> > >> + pci_dev->addr.function != pci_addr.function)
> > >> + continue;
> > >> +
> > >
> > > As far as I understand, intention of this loop is to find 'ibdev'
> > > matching this device, code gooes through all "ibv device list" for
> > > this, I wonder if there is a easy way for doing this, like a sysfs
> > > entry to help getting this information?
> > > And how mlx4/5 does this?
> >
> > Since there are multiple RDMA devices now, does it make sense to have
> > RDMA bus driver, which can hide some PCIe details under bus, and driver can
> > get PCI and ibdev information during probe?
>
> Mellanox drivers use a similar way to go through the list of IB devices.
>
> Matan, Viacheslav, what are your thoughts on implementing a bus for RDMA devices?
These are PCI devices first.
Is it a good idea to have a bus driver on top of another one?
What would be the responsibility of such a bus driver?
next prev parent reply other threads:[~2022-08-29 7:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 23:49 [Patch v4 00/17] Introduce Microsoft Azure Network Adatper (MANA) PMD longli
2022-07-08 23:49 ` [Patch v4 01/17] net/mana: add basic driver, build environment and doc longli
2022-08-22 15:03 ` Ferruh Yigit
2022-08-22 15:07 ` Ferruh Yigit
2022-08-22 18:27 ` Long Li
2022-08-29 7:58 ` Thomas Monjalon [this message]
2022-08-29 8:51 ` Ferruh Yigit
2022-08-29 9:20 ` Thomas Monjalon
2022-09-07 23:38 ` Long Li
2022-07-08 23:49 ` [Patch v4 02/17] net/mana: add device configuration and stop longli
2022-07-08 23:49 ` [Patch v4 03/17] net/mana: add function to report support ptypes longli
2022-07-08 23:49 ` [Patch v4 04/17] net/mana: add link update longli
2022-07-08 23:49 ` [Patch v4 05/17] net/mana: add function for device removal interrupts longli
2022-07-08 23:49 ` [Patch v4 06/17] net/mana: add device info longli
2022-07-08 23:49 ` [Patch v4 07/17] net/mana: add function to configure RSS longli
2022-07-08 23:49 ` [Patch v4 08/17] net/mana: add function to configure RX queues longli
2022-07-08 23:49 ` [Patch v4 09/17] net/mana: add function to configure TX queues longli
2022-07-08 23:49 ` [Patch v4 10/17] net/mana: implement memory registration longli
2022-07-08 23:49 ` [Patch v4 11/17] net/mana: implement the hardware layer operations longli
2022-08-22 15:08 ` Ferruh Yigit
2022-08-22 18:28 ` Long Li
2022-07-08 23:49 ` [Patch v4 12/17] net/mana: add function to start/stop TX queues longli
2022-07-08 23:49 ` [Patch v4 13/17] net/mana: add function to start/stop RX queues longli
2022-07-08 23:49 ` [Patch v4 14/17] net/mana: add function to receive packets longli
2022-07-08 23:49 ` [Patch v4 15/17] net/mana: add function to send packets longli
2022-08-22 15:09 ` Ferruh Yigit
2022-08-24 13:38 ` Thomas Monjalon
2022-07-08 23:49 ` [Patch v4 16/17] net/mana: add function to start/stop device longli
2022-07-08 23:49 ` [Patch v4 17/17] net/mana: add function to report queue stats longli
2022-08-22 15:08 ` Ferruh Yigit
2022-08-22 18:35 ` Long Li
2022-08-22 14:59 ` [Patch v4 00/17] Introduce Microsoft Azure Network Adatper (MANA) PMD Ferruh Yigit
2022-08-22 17:07 ` 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=1857175.eGJsNajkDb@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=longli@microsoft.com \
--cc=matan@nvidia.com \
--cc=sharmaajay@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=viacheslavo@nvidia.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).