search for: cpu21

...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...

...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...

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

...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 0 0...

...9:49 100.00% kernel{thread taskq} 2873 root 84 0 22584K 4180K CPU1 1 2:53 44.58% relayd 2879 _relayd 84 0 49128K 34268K CPU9 1 12:17 43.26% relayd 2877 _relayd 52 0 69608K 54400K kqread 22 30:07 39.45% relayd 2880 _relayd 84 0 65512K 50692K CPU21 21 23:22 39.36% relayd 2878 _relayd 52 0 57320K 42432K kqread 14 21:54 39.16% relayd 2881 _relayd 83 0 49128K 31572K CPU4 4 4:34 38.67% relayd 7607 dovecot 82 0 58036K 10528K CPU16 16 2:31 37.50% auth 3017 root 83 0 19860K 2316K CPU6 6...

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.

...U17 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: find owner on CPU23 (XEN) CMCI: CPU23 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU24 (XEN) CMCI: CPU24 owner_map[b], no_cmci_map[14] (XEN) CMCI:...

...onization unnecessary (XEN) Platform timer is 14.318MHz HPET ?(XEN) Allocated console ring of 256 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU13 resumed (XEN) microcode.c:73:d32767 microcode: CPU23 resumed (XEN) microcode.c:73:d32767 microcode: CPU21 resumed (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) microcode.c:73:d32767 microcode: CPU22 resumed (XEN) microcode.c:73:d32767 microcode: CPU10 resumed (XEN) microcode.c:73:d32767 microcode: CPU11 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 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