From: Lance G. <ei...@pa...> - 2014-12-15 22:35:50
|
Hello Quinn: I’m not sure what the different columns mean, but I believe the two ports on the card are at the same IRQs: [root@QOS ~]# ./split_irq.sh -l 34: 43 0 0 0 0 0 0 0 PCI-MSI-edge qla2xxx (default) 35: 0 0 0 0 0 0 0 0 PCI-MSI-edge qla2xxx (rsp_q) 36: 0 0 0 0 0 0 0 0 PCI-MSI-edge qla2xxx (atio_q) 37: 43 0 0 0 0 0 0 0 PCI-MSI-edge qla2xxx (default) 43: 0 0 0 0 0 0 0 0 PCI-MSI-edge qla2xxx (rsp_q) 44: 0 0 0 0 0 0 0 0 PCI-MSI-edge qla2xxx (atio_q) 34: ff 35: ff 36: ff 37: ff 43: ff 44: ff Hit any key to continue. Ctrl-C to quit Lance From: Quinn Tran Sent: Friday, December 12, 2014 9:43 AM To: Lance Gropper ; scs...@li... Subject: Re: [Scst-devel] 16Gbit not working Lance, The interrupts on the 16G adapter are different than the 8G adapter. There's additional interrupts to handle the higher load. Some OS/kernel does a good job of spreading the Interrupts across different CPUs to spread the work load. Some don't spread it. This looks like a case of where all interrupt lines are funneled to CPU 0. This require fine tuning for specific environment that you're in to get the best perf. Attached is a script I created for this case: a.. -l option: show where the interrupts are routing to by watching highlighted b.. -s option: spread the interrupts across different cpu. Use this option before test start. You're welcome to modify the script to fit your need. The setting does not persist across driver re-load or reboot. Give this a try. Will include this script into the Qlogic git tree in the future. Regards, Quinn Tran From: Lance Gropper <ei...@pa...> Date: Thursday, December 11, 2014 4:42 PM To: "scs...@li..." <scs...@li...> Subject: [Scst-devel] 16Gbit not working Hello All: I got the latest Qlogic GIT for the 16Gbit target drivers – everything builds and loads with no problems. If I attach an 8Gbit Initiator, no problems, and I can saturate the pipes at about 760MB/sec on reads and writes. If, however, I use a 16Gbit initiator, I only get about 277MB/sec on reads and writes. What’s the deal? Lance -------------------------------------------------------------------------------- This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries, divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. |