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