On Mon, 2018-02-12 at 18:04 +0000, Bart Van Assche wrote:
> On Tue, 2018-01-30 at 17:29 -0500, Doug Ledford wrote:
> > On Tue, 2018-01-30 at 18:19 +0000, Bart Van Assche wrote:
> > > Regarding configuring on which IP address to listen, one possibile approach
> > > is to move the rdma_cm_port port number configfs attribute from
> > > /sys/kernel/config/target/srpt/discovery_auth/rdma_cm_port to
> > > /sys/kernel/config/target/srpt/$port/$port/attrib/rdma_cm_port where $port
> > > is an RDMA port GUID or GID (both are accepted). That would allow to
> > > enable/disable RDMA/CM support per RDMA adapter port. The ib_srpt driver
> > > could e.g. create one listening rdma_cm_id per IP address that is associated
> > > with an RDMA port.
> >
> > That would work as well.
>
> Hello Doug,
>
> Do you prefer that the RDMA/CM port number is configurable per RDMA port
> (/sys/kernel/config/target/srpt/$port/$port/attrib/rdma_cm_port) or is a
> single attribute for all ports sufficient
> (/sys/kernel/config/target/srpt/discovery_auth/rdma_cm_port)? I'm asking this
> since there is already an attribute that allows to enable/disable SRP target
> support per RDMA port (/sys/kernel/config/target/srpt/$port/$port/enable).
I'm fine either way (sorry I missed this email until now).
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDDAttachment:
signature.asc
Description: This is a digitally signed message part
