http://bugzilla.opensuse.org/show_bug.cgi?id=1133795 http://bugzilla.opensuse.org/show_bug.cgi?id=1133795#c2 --- Comment #2 from Ruediger Oertel <ro@suse.com> --- well, first of all because Johannes told me that the latency of multipath is by order of magnitude larger than the latency for nvme devices and there only is a single path to the device anyway.... here is the udevadm info: obs-arm-4:~ # udevadm info -a /dev/nvme0n1 Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/platform/soc@0/88808f000000.pci/pci0005:8f/0005:8f:00.0/0005:90:00.0/nvme/nvme0/nvme0n1': KERNEL=="nvme0n1" SUBSYSTEM=="block" DRIVER=="" ATTR{alignment_offset}=="0" ATTR{capability}=="50" ATTR{discard_alignment}=="0" ATTR{eui}=="00 23 03 56 30 0a ea 92" ATTR{ext_range}=="256" ATTR{hidden}=="0" ATTR{inflight}==" 0 0" ATTR{make-it-fail}=="0" ATTR{nsid}=="1" ATTR{range}=="0" ATTR{removable}=="0" ATTR{ro}=="0" ATTR{size}=="2000409264" ATTR{stat}==" 7870201 0 949949631 94480710 550086975 0 129567507950 4082327024 0 1359744300 2988495358" ATTR{wwid}=="eui.00230356300aea92" looking at parent device '/devices/platform/soc@0/88808f000000.pci/pci0005:8f/0005:8f:00.0/0005:90:00.0/nvme/nvme0': KERNELS=="nvme0" SUBSYSTEMS=="nvme" DRIVERS=="" ATTRS{address}=="0005:90:00.0" ATTRS{cntlid}=="1" ATTRS{firmware_rev}=="1.07 " ATTRS{model}=="PLEXTOR PX-1TM9PeY " ATTRS{numa_node}=="0" ATTRS{serial}=="P02910108551 " ATTRS{state}=="live" ATTRS{subsysnqn}=="nqn.2014.08.org.nvmexpress:14a41b4bP02910108551 PLEXTOR PX-1TM9PeY " ATTRS{transport}=="pcie" looking at parent device '/devices/platform/soc@0/88808f000000.pci/pci0005:8f/0005:8f:00.0/0005:90:00.0': KERNELS=="0005:90:00.0" SUBSYSTEMS=="pci" DRIVERS=="nvme" ATTRS{broken_parity_status}=="0" ATTRS{class}=="0x010802" ATTRS{consistent_dma_mask_bits}=="64" ATTRS{current_link_speed}=="8 GT/s" ATTRS{current_link_width}=="4" ATTRS{d3cold_allowed}=="1" ATTRS{device}=="0x23f1" ATTRS{devspec}=="" ATTRS{dma_mask_bits}=="64" ATTRS{driver_override}=="(null)" ATTRS{enable}=="1" ATTRS{irq}=="18" ATTRS{local_cpulist}=="0-47" ATTRS{local_cpus}=="ffff,ffffffff" ATTRS{max_link_speed}=="8 GT/s" ATTRS{max_link_width}=="4" ATTRS{msi_bus}=="1" ATTRS{numa_node}=="0" ATTRS{revision}=="0x01" ATTRS{subsystem_device}=="0x1093" ATTRS{subsystem_vendor}=="0x1b4b" ATTRS{vendor}=="0x14a4" looking at parent device '/devices/platform/soc@0/88808f000000.pci/pci0005:8f/0005:8f:00.0': KERNELS=="0005:8f:00.0" SUBSYSTEMS=="pci" DRIVERS=="pcieport" ATTRS{broken_parity_status}=="0" ATTRS{class}=="0x060400" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{current_link_speed}=="8 GT/s" ATTRS{current_link_width}=="4" ATTRS{d3cold_allowed}=="1" ATTRS{device}=="0xa100" ATTRS{devspec}=="" ATTRS{dma_mask_bits}=="32" ATTRS{driver_override}=="(null)" ATTRS{enable}=="1" ATTRS{irq}=="18" ATTRS{local_cpulist}=="0-47" ATTRS{local_cpus}=="ffff,ffffffff" ATTRS{max_link_speed}=="8 GT/s" ATTRS{max_link_width}=="8" ATTRS{msi_bus}=="1" ATTRS{numa_node}=="0" ATTRS{revision}=="0x09" ATTRS{secondary_bus_number}=="144" ATTRS{subordinate_bus_number}=="144" ATTRS{subsystem_device}=="0x0000" ATTRS{subsystem_vendor}=="0x0000" ATTRS{vendor}=="0x177d" looking at parent device '/devices/platform/soc@0/88808f000000.pci/pci0005:8f': KERNELS=="pci0005:8f" SUBSYSTEMS=="" DRIVERS=="" looking at parent device '/devices/platform/soc@0/88808f000000.pci': KERNELS=="88808f000000.pci" SUBSYSTEMS=="platform" DRIVERS=="pci_thunder_pem" ATTRS{driver_override}=="(null)" looking at parent device '/devices/platform/soc@0': KERNELS=="soc@0" SUBSYSTEMS=="platform" DRIVERS=="" ATTRS{driver_override}=="(null)" looking at parent device '/devices/platform': KERNELS=="platform" SUBSYSTEMS=="" DRIVERS=="" -- You are receiving this mail because: You are on the CC list for the bug.