netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"Ertman, David M" <david.m.ertman@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"nhorman@redhat.com" <nhorman@redhat.com>,
	"sassmann@redhat.com" <sassmann@redhat.com>,
	"ranjani.sridharan@linux.intel.com" 
	<ranjani.sridharan@linux.intel.com>,
	"pierre-louis.bossart@linux.intel.com" 
	<pierre-louis.bossart@linux.intel.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"Bowers, AndrewX" <andrewx.bowers@intel.com>
Subject: RE: [net-next 2/9] ice: Create and register virtual bus for RDMA
Date: Mon, 20 Apr 2020 23:47:15 +0000	[thread overview]
Message-ID: <61CC2BC414934749BD9F5BF3D5D940449866CCA8@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <20200417191756.GJ26002@ziepe.ca>

> -----Original Message-----
> From: Jason Gunthorpe <jgg@ziepe.ca>
> Sent: Friday, April 17, 2020 12:18
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@intel.com>
> Cc: davem@davemloft.net; gregkh@linuxfoundation.org; Ertman, David M
> <david.m.ertman@intel.com>; netdev@vger.kernel.org; linux-
> rdma@vger.kernel.org; nhorman@redhat.com; sassmann@redhat.com;
> ranjani.sridharan@linux.intel.com; pierre-louis.bossart@linux.intel.com; Nguyen,
> Anthony L <anthony.l.nguyen@intel.com>; Bowers, AndrewX
> <andrewx.bowers@intel.com>
> Subject: Re: [net-next 2/9] ice: Create and register virtual bus for RDMA
> 
> On Fri, Apr 17, 2020 at 10:10:27AM -0700, Jeff Kirsher wrote:
> > From: Dave Ertman <david.m.ertman@intel.com>
> >
> > The RDMA block does not have its own PCI function, instead it must
> > utilize the ice driver to gain access to the PCI device. Create a
> > virtual bus device so the irdma driver can register a virtual bus
> > driver to bind to it and receive device data. The device data contains
> > all of the relevant information that the irdma peer will need to
> > access this PF's IIDC API callbacks.
> 
> Can you please provide examples of what the sysfs paths for all this stuff looks
> like?
[Kirsher, Jeffrey T] 

Here is an example using ice and irdma driver registered:
/sys/bus/virtbus/devices/intel,ice,rdma.7
/sys/bus/virtbus/devices/intel,ice,rdma.5
/sys/bus/virtbus/devices/intel,ice,rdma.6
/sys/bus/virtbus/devices/intel,ice,rdma.4
/sys/bus/virtbus/drivers/irdma/intel,ice,rdma.7
/sys/bus/virtbus/drivers/irdma/intel,ice,rdma.5
/sys/bus/virtbus/drivers/irdma/intel,ice,rdma.6
/sys/bus/virtbus/drivers/irdma/intel,ice,rdma.4
/sys/devices/pci0000:00/0000:00:1c.4/0000:09:00.0/intel,ice,rdma.4
/sys/devices/pci0000:00/0000:00:1c.4/0000:09:00.3/intel,ice,rdma.7
/sys/devices/pci0000:00/0000:00:1c.4/0000:09:00.1/intel,ice,rdma.5
/sys/devices/pci0000:00/0000:00:1c.4/0000:09:00.2/intel,ice,rdma.6
/sys/module/virtual_bus/holders/ice
/sys/module/ice
/sys/module/ice/drivers/pci:ice
/sys/bus/pci/drivers/ice

/sys/bus/virtbus/drivers/irdma
/sys/module/virtual_bus/holders/irdma
/sys/module/irdma
/sys/module/irdma/drivers/virtbus:irdma
/sys/module/ib_core/holders/irdma
/sys/module/ib_uverbs/holders/irdma

> 
> Does power management work right?
[Kirsher, Jeffrey T] 

The power management we tested so far is working.  Are you seeing any issue?

> 
> Jason

  reply	other threads:[~2020-04-20 23:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 17:10 [net-next 0/9][pull request] 100GbE Intel Wired LAN Driver Updates 2020-04-17 Jeff Kirsher
2020-04-17 17:10 ` [net-next 1/9] Implementation of Virtual Bus Jeff Kirsher
2020-04-17 19:14   ` Pierre-Louis Bossart
2020-04-17 19:51   ` Jason Gunthorpe
2020-04-20 23:16     ` Ertman, David M
2020-04-21  0:44       ` Jason Gunthorpe
2020-04-21 23:27         ` Ertman, David M
2020-04-18 12:50   ` Greg KH
2020-04-20 22:59     ` Ertman, David M
2020-04-21  6:52       ` Greg KH
2020-04-20 23:46   ` Ranjani Sridharan
2020-04-17 17:10 ` [net-next 2/9] ice: Create and register virtual bus for RDMA Jeff Kirsher
2020-04-17 19:17   ` Jason Gunthorpe
2020-04-20 23:47     ` Kirsher, Jeffrey T [this message]
2020-04-17 23:49   ` Jason Gunthorpe
2020-04-17 17:10 ` [net-next 3/9] ice: Complete RDMA peer registration Jeff Kirsher
2020-04-17 17:10 ` [net-next 4/9] ice: Support resource allocation requests Jeff Kirsher
2020-04-17 17:10 ` [net-next 5/9] ice: Enable event notifications Jeff Kirsher
2020-04-17 17:10 ` [net-next 6/9] ice: Allow reset operations Jeff Kirsher
2020-04-17 17:10 ` [net-next 7/9] ice: Pass through communications to VF Jeff Kirsher
2020-04-17 17:10 ` [net-next 8/9] i40e: Move client header location Jeff Kirsher
2020-04-17 17:10 ` [net-next 9/9] i40e: Register a virtbus device to provide RDMA Jeff Kirsher

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=61CC2BC414934749BD9F5BF3D5D940449866CCA8@ORSMSX112.amr.corp.intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=andrewx.bowers@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=david.m.ertman@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sassmann@redhat.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).