00:10:48 i40e, ice, and others of its ilk (my recollection is that bnxt started this trend) is that it's the HW-RAID of networking. "Can't you just let crossbow do all of this?" is networking's equivalent of, "Can't you just let ZFS do all of this?" 01:47:33 I appreciate anytime I set the MTU to 9000 and it works.... This stuff is complicated lol 01:47:54 I started to read about "virtual station interface" rofl 01:51:48 Downloading the Datasheet and trying to pretend to understand :) 02:10:23 which? 02:11:24 the x710 https://statics.teams.cdn.office.net/evergreen-assets/safelinks/2/atp-safelinks.html 02:11:45 sigh.... thats what I get for copying from TEAMS 02:12:15 errrrrrr https://www.intel.com/content/www/us/en/support/articles/000093196/ethernet-products.html 02:12:30 you know, there are easier cures for insomnia :) 02:12:48 bahahahahah 02:13:18 Its helped with exercise...., I thought I'd rather do anything other than run .... 02:14:58 i mean, at the core if like practically every NIC, there's one or more rings, which is just an array (just when you write the last entry, you wrap around and start writing at the first one, hence the term) 02:15:31 and basically every element has a field for the physically address of the data to send and a length, and usuaully some other flags depending on features 02:15:59 often one to indicate which entry is the last one of the packet (so a packet can be split across multiple entries) 02:16:13 then you write the index of the first packet somewhere to send 02:17:20 and on the receive side, you just write the physical address and size of a bunch of memory you preallocate, then when a packet comes in, there's an interrupt and you can read a register that says which entry is the first one (and again usually there's a flag to say the last one) 02:17:24 or some variation 02:17:34 it's just all the _other_ stuff you have to do to get to that point 02:17:51 (which for those cards is quite a bit) 02:18:18 plus they have a built in network switch, so those different rings can basically at like virtual NICs on their own and do switching 02:18:49 (but then you have to worry about well which ones are in the same broadcast domain.. which mac addresses are allowed where, etc) 02:19:08 and for the intel nics, you also have to deal with their horrible LSO implementation :) 02:20:05 (horrible in the sense the amount of work you have to put in to use it almost gets to the point of not being worth it just because you've done like 70% of the work already) 02:22:41 And I'm guessing the affinity for the chelsio cards comes from them not being as much work? 02:22:54 unfortuantely, i've not had a chance to use them 02:23:12 but it does seem like they're working with those that are using them 02:23:24 so I can't say 02:23:45 but i'd hope their LSO support isn't nearly as annoying as Intel's 02:24:02 though I understand they can do quite a few other offloads if you want... 02:24:36 (I kinda wish we'd look at them... just like someone wants dell or hp, and basically they both go 'your choices are broadcom or intel' 05:53:33 [illumos-gate] 18220 mdb: 'end' may be used uninitialized -- Toomas Soome 17:05:55 any crontab experts here? I'm trying to understand this part of the crontab(1) manpage: 17:05:58 The sixth field of a line in a crontab file is a string that is 17:05:58 executed by the shell at the specified times. A percent character in 17:05:58 this field (unless escaped by \) is translated to a NEWLINE character. 17:06:25 I'm hoping someone, somewhere, has an example. My goal is to have a job fire at 01:42 on the first Saturday of the month. 17:07:08 I have first Sunday of the month jobs like: 17:07:10 0 1 1-7 * * [ `date +\%a` = Sun ] && zpool scrub rpool 17:07:21 I'm testing with: 03 10 * * 3 [ 'date +\%d' -le 8 ] 17:08:01 but I'm getting email saying [: missing or similar. When I add : to the [ I get an error about [:: not found. 17:08:50 oh bother, never mind. Google was leading me way, way astray. 17:08:57 forget I said anything. I hid my head in shame. 17:09:01 Yours seems to be missing the space after the [ and using ' instead of ` (backticks) 17:10:04 Google was implying that the sixth field was part of the cron smarts, not just the script-to-be-executed. 17:10:13 so I was barking up the wrong forest. 17:10:48 (as in, the ai summary was totally messed up and I was messed up for trying to understand it) 17:13:33 andyf, your job is *exactly* what I'm trying to do, just different day. :) 17:14:00 i should get back to working on svc.periodicd at some point... just between the xml parsing, xml manifest additions, and libscf pieces, it's sooooooo tedious i can only manage small bits at a time :) 17:14:32 * ENOMAD yoinks andyf's work 17:19:50 It's a good thing I have a meeting now. I can't do anything else really stupid for at least an hour. 19:00:14 [illumos-gate] 18003 poll(4D) needs to better-check numfds (CVE-2026-35384) -- Andy Fiddaman 19:00:14 [illumos-gate] 18020 Double copyin of dld_ioc consumers -- Dan McDonald 19:00:14 [illumos-gate] 18117 SCTP needs to better-check INIT ACK chunk parameters -- Dan McDonald 19:05:49 Start your distro builds folks! 19:20:03 heh.. 19:20:10 was doing that as you typed :) 19:21:04 granted, i don't run anything untrusted locally (or give untrusted access to anything), but why take a chance 19:21:40 (i run a slightly customized smartos at home) 19:33:05 please tell me this is a remote exploit and I don't have to do anything for my no-users-allowed file servers. 19:33:13 . o O ( la la la I can't hear you ) 19:34:36 you mean don't tell you? 19:35:10 from the looks of it, only the SCTP one is something that could be triggered remotely (but probably only if you're running something that's listening for SCTP stuff) 19:35:15 which is probably unlikely 19:35:34 jbk no, you don't need to be running anything that's listening for SCTP 19:35:54 oh that's really unfortunate 19:36:38 ... and something seems to be broken with building the latest smartos 19:38:33 hrm... looks like 18043 introduced a flag day I might have missed 19:39:13 (or the 'native' smf build has bugs) 19:51:16 fenix illumos 18043 19:51:18 FEATURE 18043: want libscf smf_XXX_instance variants that take a scf_instance_t (Closed) 19:51:18 ↳ https://www.illumos.org/issues/18043 | https://code.illumos.org/c/illumos-gate/+/4683 20:02:29 * ENOMAD sighs "I'm glad I have patient users who understand the need to patch for security" 20:02:38 (and no, that wasn't sarcastic. I'm *really* lucky.) 20:11:57 uugh 20:12:08 the rather byzantine I/O path through sd.c can be annoying