00:21:12 hrm.. there's not an easy way to go from a disk that's an NVMe namespace and go back to the corresponding controller device, is there? 00:21:31 aside from iterating all of the nvme controllers and enumerate all the namespaces and cache the results 00:28:30 jbk: That's basically what I did recently: https://gist.github.com/jclulow/ff8a4c8e256258e7f0ffbe2027479841 00:33:54 hrm.. actually.. could you use libdevinfo and just look at the name of parent node of each blkdev device.... 00:36:14 i think that's kinda what you're doing (with some additional considerations for your hw) if i'm reading that correctly.. but just using /devices 00:38:34 got to figure out what will be the least painful in go (unfortunately.. it's such an ill-fit for lower level stuff) 00:52:12 Ah yeah, in my case I actually need to know the attachment point ID 00:52:15 a la libcfgadm/cfgadm 00:52:47 as well as /devices and /dev/dsk and nvmeN 19:16:58 rmustacc: you started work on an ice (intel 810) driver, right? 22:13:08 That sounds accurate 22:28:00 it looks like a number of newer servers now come with those built-in, so might be looking to pick up that work (if no one else does)... 22:28:50 from the datasheet, it seems fairly similar to i40e (complete with it's annoying DMA limitations for LSO) 22:29:02 just with rdma support now 22:31:03 oh, Intel has a new product called Intel 810, I guess it has been 25 years since they shipped Intel 810 graphics 22:32:09 https://en.wikipedia.org/wiki/Intel_810 22:42:29 yeah, it's another NIC