I haven't tracked new things there, only hope that the IDs are right. But I just wonder about naming uniformity: previously we've already had "_H_" in constant names, while we never had "_U_".

As with any other patches of the kind you may either fix the "issue" or break sound completely by producing invalid configuration. Unless the configuration is already broken and require fixing, it should better be handled with /dev/dsp redirection, as we discussed before.

RGB mode looks like some magic withe the number of constants. I wonder if it is possible or reasonable to read defaults from BIOS where the changed values are stored?

Seems to make sense, but I don't know anything about it.

I have no objections, but I wonder whether maximum of 3 vs 7 might be model-specific?

I have no objections, if it works, but I don't have that ASUS for quite a while now.

Just to be sure, DA_FLAG_PACK_INVALID does not mean there is no media. There might be a media, just not one we opened originally.

This change require DA_FLAG_PACK_INVALID to be reliable avoid false periph invalidations. I am not sure current asc == 0x3a covers all the cases, I have feeling that 0x28/0x00 Not ready to ready change, medium may have changed is even more widespread case of media change and so pack invalidation.

This change is unneeded. ascq <= table_entry->ascq is already checked few lines above.

I've noticed this issue too while looking on the previous patch.

In D48595#1109250, @jhb wrote:

I'm not quite sure where to put the nvlist_error calls TBH.

I don't remember nvlists much, but shouldn't errors be checked via nvlist_error() sometimes?

I guess instead of 1 could be expected some error codes, that just never happened.

This seems consistent with other places where we use "SS_FATAL | ENXIO".

While I guess u3g.4 might indeed include the full list of supported devices, simply because IIRC many of them require some quirks to attach and operate, the snd_hda was written with a goal to work on unknown hardware. The list of devices in the code in most cases is just for cosmetics and user convenience. That is why I would not like it to be listed as more than examples. We've actually had a list in the man page before, but I axed it out at some point.

I understand the desire to avoid extra work, but if server load pattern really change to no longer require the KTLS, the allocations will stay cached, occupying memory for no reason if there is no explicit pressure. For example, considering ZFS might shrink ARC or at least limit its growth if there is no free memory, it might be a waste.

I don't remember whether ASPM has anything to do with enabling ports, so wonder if it is a curios case of opposite bugs, but if it helps, I see no problem.

I've never used it myself, so don't have a strong opinion, but as next step somebody will want to block reservation conflicts, then something else, and again and again...

Looks good to me. Thanks.

The xpt_done_td queues are used only for the non-MP safe things as well as I think for the error path, both of which are relatively rare.

In D46469#1059445, @jrtc27 wrote:

What do you both think of https://reviews.freebsd.org/P646 as a more systematic way of addressing this?

I suppose 3 printf's may cause garbled output if other printf's are used by something.

It seems BIO_GETATTR allows GEOM::attachment override. Though I am not saying it is very useful.

Looks fine to me, just couple nits.

Have you looked on similar Linux code? It would be good to be consistent or at least similar. I haven't looked deep, but foreach_nfs_host_cb() seems to support multiple hosts.

Looks odd to me, but OK.

In D45660#1042742, @ken wrote:

So here is what the debugging log message in isp_getpdb() shows. isp0 and isp1 are connected to LTO-6 tape drives via an 8Gb switch. isp2 is directly connected to an LTO-6 in loop mode:

isp0: Chan 0 handle 0x0 Port 0xfffc01 flags 0x0 curstate 77 laststate 77
isp0: Chan 0 handle 0x1 Port 0x011b26 flags 0x40a0 curstate 46 laststate 46
isp0: Chan 0 handle 0x7fe Port 0xfffffe flags 0x0 curstate 44 laststate 44
isp0: Chan 0 handle 0x7fe Port 0xfffffe flags 0x0 curstate 44 laststate 44
isp1: Chan 0 handle 0x0 Port 0xfffc01 flags 0x0 curstate 77 laststate 77
isp1: Chan 0 handle 0x1 Port 0x011a26 flags 0x40a0 curstate 46 laststate 46
isp1: Chan 0 handle 0x7fe Port 0xfffffe flags 0x0 curstate 44 laststate 44
isp1: Chan 0 handle 0x7fe Port 0xfffffe flags 0x0 curstate 44 laststate 44
isp2: Chan 0 handle 0x0 Port 0x000026 flags 0x40a0 curstate 46 laststate 46

It seems a good tunable, except I am not getting the meaning of "only" there. Why not "always", "force" or something like that?

None of QLogic documents I have know nothing about NVMe, and this state field is declared is byte there. I have no objections for this patch, but a bit curios what NVMe status do we see there for non-NVMe devices.

Differences of less than 4 (RQ_PPQ) are insignificant and are simply removed. No functional change (intended).

I suspect that first thread was skipped to avoid stealing a thread that was just scheduled to a CPU, but was unable to run yet.

I am not fully sure about the motivation of this change, but It feels wrong to me to have per-namespace zones. On a big system under heavy load UMA does a lot of work for per-CPU and per-domain caching, and doing it also per-namespace would multiply resource waste. Also last time I touched it, I remember it was difficult for UMA to operate in severely constrained environments, since eviction of per-CPU caches is quite expensive. I don't remember how reservation works in that context, but I suppose that having dozens of small zones with small reservations, but huge per-CPU caches is not a very viable configuration.

I see no problems, but I have difficulties to believe that timeout handlers 1-2 times per second per queue pair may have any visible effects. Also I am not happy to see second place where timeouts are calculated. And 99/100 also looks quite arbitrary.

Mechanically it seems to have sense. I've missed when than original transition happened, but if you say it is right, so be it.