09:04:17 any recommendations for [single port] ethernet adapter? should support 1, 2.5, 10 Gbit. I guess, something like intel x500 series maybe? 14:37:07 tsoome_: What interface? Copper or SFP? 15:00:31 I wish you all fast acceleration for the new year 2024. 15:24:44 rmustacc copper 15:25:09 Cheers, getting a bit lost with HDD technologies and implications for ZFS in particular (e.g. that debacle with CCTV oriented disks that were poor choice for random I/O) - which key words are "good" or "bad" nowadays? :) 15:25:32 looking to update my home system 15:25:49 Looking at Western Digital Ultrastar DC HC580, 3.5", 24TB I see both "CMR" and "EAMR" mentioned - are those "okay"? :) 15:26:30 Likewise, pondering a home NAS update :) 15:34:01 yes and stormont and woodstock 15:34:09 oops, wc 16:18:31 tsoome_: I'm using X550T2 for OmniOS on Supermicro Board (Intel X3) 16:20:25 tsoome_: in 10Gbit mode with switch Netgear S512EM-100EUS - a small Office Setup where a Samba Server make file service. 16:24:06 jimklimov: as I understand it, CMR good, SMR bad. C="Conventional" non-overlapping tracks that can be written in any order. S="Shingled" overlapping tracks, where within a drive-defined track group the drive must write sequentially (with much buffering and added latency if the drive firmware tries to hide this from the host). EAMR+CMR should be good. 16:27:29 even if an SMR drive presents it as a conventional block device (as opposed to zone storage), zfs really doesn't deal with it well at all (as much as you'd think it'd actually be a good fit) 16:27:36 SMR comes in two flavors: drive-managed and host-managed. host-managed requires special software to enforce the correct write ordering. drive-managed tries to hide the complexity in hardware but can't hide the latency hit. 16:29:30 jbk: IMHO the missing interface for drive-managed SMR is some sort of indication from the drive of how backlogged it is. 16:31:32 I should have said "hide the complexity in firmware". 16:33:57 IIRC a ZFS resilver on a "dirty" drive is a worst-case workload for SMR. Unending stream of writes, mostly not well-aligned with the SMR zones. 16:34:52 even then, i suspect some of the other bookkeeping bits of zfs just don't play well.. or at least HDDs are just too slow 16:35:09 on linux you can do that 'hide the complexity' at the device layer, and zfs still has lots of problems w/ it 16:36:21 tomww thanks, I was looking for something similar:) 16:50:23 thanks all! happy holidays :) 16:55:07 tsoome_: hm? 17:23:58 jbk: yeah, I suspect the flow control needs to extend upwards into ZFS. 18:26:13 unfortunately, zfs itself doesn't seem equipped for such things 18:26:28 we've hit several problems that end up all being variants of 'zfs has no concept of backpressure' 18:27:06 e.g. prefetching can exhaust all ram if your disk isn't fast enough 18:37:50 Does Sun make (the default of OI/OO/...) have some syntax for exporting make vars as envvars to launched programs? GNU/BSD both support `export VAR=VAL` but not Sun :\ 18:48:13 The `man make` page a bit cryptically says that: 18:48:13 make exports environment variables, using the most recently defined value. Macro definitions supplied on the command line are not normally exported, unless the macro is also an environment variable. 18:48:13 make does not export macros defined in the makefile. If an environment variable is set, and a macro with the same name is defined on the command line, make exports its value as defined on the command line. 18:50:49 so I guess if I go either `VAR=VAL make`, or `export VAR ; make VAR=VAL` or `export VAR; make` (and have `VAL=VAR` assigned as a macro in the makefile) then it gets exported further to build toolkit programs - but only then, if the caller shell takes care to export them? 19:25:55 jbk: yep. 13093 covers a few. And (after a few panics during a weekly scrub) I added one that throttles scrub when freemem is low. 19:30:21 jimklimov: while it doesn't directly answer your question, note the -e option to make (which imports environment variables into make) 19:30:52 jimklimov: in the make rule you can set environment variables for the specific command. 19:30:58 test: 19:31:14 FOO=${BAR} printenv FOO 19:32:09 (the usual /bin/sh syntax for per-command environment variables) 19:35:37 yeah, but in my case I want something applied for any use-case of a $(CC) or $(CXX) 19:36:42 technically, they can be (symlinks to) ccache and I want certain CCACHE_* envvars applied whenever a developer re-runs `make` in the configured workspace while iterating, without requiring that stuff is pre-exported in their shell 19:38:02 I can surely pre-export them in a CI wrapper script which does autogen+configure+make dance, but for interactive use it is cumbersome compared to editing a file and writing `make` anywhere relevant in the build tree 19:58:34 you can actually stuff the environment variable settings inside $(CC) or $(CXX) if you're feeling sufficiently twisted.