I see i40e keeps on giving gifts to danmcd :(

oh to everyone

a lot of our stuff have them in there

Sadly my main server at home has them on the motherboard too :(

ixgbe been treating me way better

hrm.. silly question.. in a number of .s files, we seem to define certain instructions using .byte vs. teh symbolic name, is that just a case of 'older compilers didn't know about it', or was there some other reason

(e.g. `.byte 0x0f, 0x01, 0xf9` vs. `rdtcp`)

err rdtscp

pretty certain that was to accomodate older compilers

presumably studio & friends?

Yeah it'll be for old tools that did not have a way to symbolically assemble those things

If the current gas we're using is able to deal with the instruction I don't think there is any reason to keep doing it

hrm.. this seems likely obvious in restrospect, but I'm guessing that when BUS_UNCONFIGURE_{ONE,ALL} is called, that means the relevant child[ren] have already had their detach methods called..

at least if i'm reading this correctly

jbk: I would think they probably had to have had that, yes

Because detach is fallible

If I refuse to detach, I don't think my parent should unconfigure me

sound like poor upbringing

ha

haha

pfexec dr_phil

[illumos-gate] 15009 Update tzdata to 2022d -- Andy Fiddaman <illumos⊙fn>

lol

[illumos-gate] 15010 September 2022 hwdata update -- Andy Fiddaman <illumos⊙fn>

oh interesting..

if i'm understanding this table correctly

then my idea is maybe not so horrible

famous last words?

just what i mentioned on the i40e on the list

at least according to the x710 programming guide, it claims that intels drivers for other os's use power of two sized buffers

It would definitely be better if the device was able to pool buffers for use with many different concurrent classification filters

and also to combine buffers so that they don't all have to be full MTU sized

seems like if you're going to make a NIC this complex, it should at least be able to manage that