search for: cpu19

...ly uses one of them to process trivial network thins, > and others to transmit/receive data. > > So, in this case, it seems to driver need to touch the IRQ numbers. > > wr-linux:~ # cat /proc/interrupts > CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 > ...... > 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 > 101: 2 0 0 0 0 0 302830...

...ly uses one of them to process trivial network thins, > and others to transmit/receive data. > > So, in this case, it seems to driver need to touch the IRQ numbers. > > wr-linux:~ # cat /proc/interrupts > CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 > ...... > 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 > 101: 2 0 0 0 0 0 302830...

On Wednesday 30 July 2014, Yijing Wang wrote: > >>> > >>> The other part I'm not completely sure about is how you want to > >>> have MSIs map into normal IRQ descriptors. At the moment, all > >>> MSI users are based on IRQ numbers, but this has known scalability problems. > >> > >> Hmmm, I still use the IRQ number to map the

On Wednesday 30 July 2014, Yijing Wang wrote: > >>> > >>> The other part I'm not completely sure about is how you want to > >>> have MSIs map into normal IRQ descriptors. At the moment, all > >>> MSI users are based on IRQ numbers, but this has known scalability problems. > >> > >> Hmmm, I still use the IRQ number to map the

...gs. Eg. network driver generally uses one of them to process trivial network thins, and others to transmit/receive data. So, in this case, it seems to driver need to touch the IRQ numbers. wr-linux:~ # cat /proc/interrupts CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 ...... 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 101: 2 0 0 0 0 0 302830488 0...

...0K 384K CPU14 14 18.3H 32.08% idle{idle: cpu14} 11 root 155 ki31 0K 384K RUN 6 18.4H 31.88% idle{idle: cpu6} 11 root 155 ki31 0K 384K RUN 1 18.4H 31.79% idle{idle: cpu1} 11 root 155 ki31 0K 384K RUN 19 18.3H 31.59% idle{idle: cpu19} 11 root 155 ki31 0K 384K RUN 8 18.4H 30.96% idle{idle: cpu8} 7619 dovenull 81 0 59048K 32864K CPU20 20 2:01 30.96% imap-login 11 root 155 ki31 0K 384K CPU18 18 18.3H 30.76% idle{idle: cpu18} 11 root 155 ki31 0K 384K RUN 1...

I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated.

...owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU16 (XEN) CMCI: CPU16 owner_map[fffeb], no_cmci_map[14] (XEN) CMCI: find owner on CPU17 (XEN) CMCI: CPU17 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU18 (XEN) CMCI: CPU18 owner_map[b], no_cmci_map[14] (XEN) CMCI: find owner on CPU19 (XEN) CMCI: CPU19 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU20 (XEN) CMCI: CPU20 owner_map[b], no_cmci_map[14] (XEN) CMCI: find owner on CPU21 (XEN) CMCI: CPU21 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU22 (XEN) CMCI: CPU22 owner_map[b], no_cmci_map[14] (XEN) CMCI:...

...XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) microcode.c:73:d32767 microcode: CPU17 resumed (XEN) microcode.c:73:d32767 microcode: CPU5 resumed (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU18 resumed (XEN) microcode.c:73:d32767 microcode: CPU19 resumed (XEN) microcode.c:73:d32767 microcode: CPU15 resumed (XEN) microcode.c:73:d32767 microcode: CPU7 resumed (XEN) microcode.c:73:d32767 microcode: CPU4 resumed (XEN) microcode.c:73:d32767 microcode: CPU12 resumed (XEN) microcode.c:73:d32767 microcode: CPU14 resumed (XEN) microcode.c:73:d32767...

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so