On 26/03/17 03:52, Alan Mackenzie wrote:
Hello, Adam.
On Mon, Mar 20, 2017 at 17:09:15 +1100, Adam Carter wrote:
That, indeed, seems to to be the case. When I do cat /proc/interrupts |
egrep '(CPU/nvm)', I get just the header line with one data line:
CPU0 CPU1 CPU2 CPU3
17: 0 0 15 14605 IO-APIC 17-fasteoi
ehci_hcd:usb1, nvme0q0, nvme0q1
I'm kind of feeling a bit out of my depth here. What are the nvme0q0,
etc.? "Queues" of some kind? You appear to have nine of these things,
I've just got two. I'm sure there's a fine manual I ought to be
I have been looking at this as my MS surface (built in nvme) has been
showing two queue's similar to the above. Turns out that in order to
successfully hibernate to disk (and put extra delays in the initrd) on a
surface you have to boot on a single cpu (maxcpus=1) and then turn on
the rest once past the resume or before the suspend stages. If booting
with all cpu's enabled the queues are as expected.
Is there a way to manipulate the queues themselves in a similar way to
individual cpu's?
BillK
