On Wed, Dec 2, 2009 at 6:59 PM, Arputham Benjamin <[email protected]> wrote: > Hi, > > I suggest we add a text based name to an IB subnet, perhaps to > help user in identifying an IB subnet or understanding its function > in a multi-fabric IB cluster. For example, in a dual-fabric > (or dual-rail) IB cluster, one subnet could be named "mpi" and the > other subnet could be named "storage". > > In the current implementation of OpenSM, syslog messages are prefixed > with the process ID. When multiple instances of OpenSM run on a single node > to support dual-fabric IB, process ID doesn't help the admin to quickly > identify a specific IB subnet (i.e., it needs a translation) > > subnet_prefix (64-bit number) can be used as a prefix to syslog messages > but a user configurable text based name is better. > > We could add an option '-n | --ib_subnet_name' to OpenSM command line > to input the IB subnet name and modify the osm_log() function for syslog > messages (message type: OSM_LOG_SYS) to prefix its messages with the > subnet name.
Support for this could/should be added in the options file as well. -- Hal > Also, we could limit this name prefix changes to syslog messages only for now. > (i.e., leave the opensm log as it is because the current implementation > allows the user to specify the file name for the opensm log) > > Any comments? > > Regards, > Benjamin > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
