hello, can't get mellanox connectx-6 40GBE Card to around 5 to 6 Gbits/sec any hints ? /kernel/drv/mlxcx.conf already 'tuned'

mean mellanox Card only gives 5 to 6 Gbits/sec

@jbk --> piadm isn't smart enough to do that yet, but it is only smart enough to check on creation time.

danmcd: ahh ok.. i had been using a pre-piadm hacked up 'boot from local disk' setup and finally wanted to make the switch

turns out i had left space for the EFI partition on the l2arc/slog device anyway.. so just created it

Cool.

also have another system (that's slightly remote) in the same boat, and wanted to try conversion on my local machine first

esp since i goofed the bootloader config when updating the PI, and it was a bit tedious trying to recall all the things to set to get it to load, so want to convert that one too :)

since that one was apparently old enough that the .4th file didn't have the set-platform word(? I think that's the right term)

has anyone attempted an openindiana install on x86 mac mini hardware?

[illumos-gate] 15190 libofmt: comparison of integers of different signs -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15193 libdladm: sizeof-pointer-memaccess -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15197 libdladm: enumeration values not handled in switch -- Toomas Soome <tsoome⊙mc>

Dammit Exchange (or Mail.app)...

[illumos-gate] 9293 bootadm: empty line between boot entries in menu.lst cause bootadm list-menu to segfault -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15201 bootadm list-menu segfaults for non-existent datasets -- Toomas Soome <tsoome⊙mc>

does anything actually use the reserved partition on zfs disks? libefi has some comments, but I can't seem to find anything in the kernel that actually touches it

I believe tsoome does for boot-y purposes

nono

oh, is that a separate area?

reserved partition is used to store the fabricated device id

on MBR+VTOC layout, the alternate sectors are used for the same purpose

Yeah the devid goes in there when we make one up

Whether we make one up or not though is generally I think left up to the disk driver itself

yep

Probably that should be a bit more common-code-ish

the code for it is in usr/src/common/devid

Well, by that I mean: it feels like in the cases where we don't have a devid for the disk, maybe cmlb should just make one up uniformly and put it in the right place

rather than leaving it up to the driver

Or at least we should do it uniformly

e.g., maybe blkdev should be doing it