public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Tinsley <btinsley@emageon.com>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Gigabit/SMP performance problem
Date: Mon, 06 Jan 2003 13:26:15 -0600	[thread overview]
Message-ID: <3E19D857.4030403@emageon.com> (raw)
In-Reply-To: 23239.1041880161@www5.gmx.net

I've been able to distribute IRQ servicing to other processors on P4 
Xeon HT systems as described in the IRQ-affinity.txt file in the 
kernel-source Documentation directory. Well, it shows up as doing so in 
/proc/interrupts anyway! Looks like CPUs 0, 2, 4, etc.. are the real 
processors and 1,3,5, etc.. are the logical processors (which do not 
handle interrupts).


Daniel Blueman wrote:

>Even with HT turned off on this dual-Xeon box, all IRQs are routed to CPU 0.
>
>Kernel here is the latest RedHat 2.4.18 one.
>
>Just curious what kernel Avery is running...
>
>Dan
>
>  
>
>>On 4 Jan 2003, Daniel Blueman wrote:
>>
>>    
>>
>>>It's interesting you have IRQs balanced over the two logical
>>>processors. I can't get this on HT Xeons with stock RedHat 7.3 kernel.
>>>      
>>>
>>I think he's using two physical processors, if by "logical processors" you
>>are thinking HT... I also recall he has HT off, but the original post
>>isn't handy.
>>
>>    
>>
>>>Can you post the exact kernel version string, please?
>>>
>>>TIA,
>>>  Dan
>>>
>>>"Avery Fay" <avery_fay@symantec.com> wrote in message
>>>      
>>>
>news:<OF256CD297.9F92C038-ON85256CA3.006A4034-85256CA3.00705DEA@symantec.com>...
>  
>
>>>>Dual Pentium 4 Xeon at 2.4 Ghz. I believe I am using irq load
>>>>        
>>>>
>>balancing as 
>>    
>>
>>>>shown below (seems to be applied to Red Hat's kernel). Here's 
>>>>/proc/interrupts:
>>>>        
>>>>
>>-- 
>>bill davidsen <davidsen@tmr.com>
>>  CTO, TMR Associates, Inc
>>Doing interesting things with little computers since 1979.
>>
>>    
>>
>
>  
>

-- 

-[========================]-
-[      Brian Tinsley     ]-
-[ Chief Systems Engineer ]-
-[        Emageon         ]-
-[========================]-





  reply	other threads:[~2003-01-06 19:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b8ce5e32.0301040439.7bdaa903@posting.google.com>
2003-01-06 18:27 ` Gigabit/SMP performance problem Bill Davidsen
2003-01-06 19:09   ` Daniel Blueman
2003-01-06 19:26     ` Brian Tinsley [this message]
2003-01-08 21:44 Ronciak, John
2003-01-09 12:49 ` Robert Olsson
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 21:12 Feldman, Scott
2003-01-08 12:17 Jon Burgess
2003-01-06 20:38 Avery Fay
2003-01-07 18:15 ` Robert Olsson
2003-01-06 20:33 Avery Fay
2003-01-06 20:29 Avery Fay
2003-01-06 21:23 ` Martin J. Bligh
2003-01-07 17:19   ` Mike Black
2003-01-06 20:25 Avery Fay
2003-01-03 20:25 Avery Fay
2003-01-03 21:19 ` Arjan van de Ven
2003-01-03 21:36 ` Martin J. Bligh
2003-01-03 22:31   ` Andrew Theurer
2003-01-03 16:12 Avery Fay
2003-01-03 18:05 ` Martin J. Bligh
2003-01-03 21:49   ` Ron cooper
2003-01-03 21:47     ` Martin J. Bligh
2003-01-03 21:20 ` Robert Olsson
2003-01-04  3:33 ` Anton Blanchard
2003-01-06 19:43 ` Jon Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E19D857.4030403@emageon.com \
    --to=btinsley@emageon.com \
    --cc=daniel.blueman@gmx.net \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox