linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "JaniD++" <djani22@dynamicweb.hu>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: irq balancing question
Date: Thu, 17 Nov 2005 09:28:56 +0100	[thread overview]
Message-ID: <003d01c5eb51$3abb29f0$a700a8c0@dcccs> (raw)
In-Reply-To: 88056F38E9E48644A0F562A38C64FB6006A225B1@scsmsx403.amr.corp.intel.com


----- Original Message ----- 
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, December 15, 2005 3:00 PM
Subject: RE: irq balancing question


> >> >----- Original Message ----- 
> >> >From: "Arjan van de Ven" <arjan@infradead.org>
> >> >To: "JaniD++" <djani22@dynamicweb.hu>
> >> >> On Wed, 2005-12-14 at 22:05 +0100, JaniD++ wrote:
> >> >> > Hello, list,
> >> >> >
> >> >> > I try to tune my system with manually irq assigning, but
> >> >this simple not
> >> >> > works, and i don't know why. :(
> >> >> > I have already read all the documentation in the kernel
> >> >tree, and search
> >> >in
> >> >> > google, but i can not find any valuable reason.
> >> >>
> >> >>
> >> >> which chipset? there is a chipset that is broken wrt irq
> >balancing so
> >> >> the kernel refuses to do it there...
> >> >
> >> >This happens all of my systems, with different hardware.
> >> >
> >> >In the example is Intel SE7520AF2,  IntelR E7520 Chipset, +2x
> >> >Xeon with HT.
> >> >
> >> >And the other systems is Abit IS7, intel 865, and only one P4
> >> >CPU with HT,
> >> >but the issue is the same.
> >> >
> >>
> >> Which kernel and which architecture (i386 or x86-64?)
> >
> >i386, and kernel 2.6.14 - 2.6.15-rc3
>
> Things should work with 2.6.15-rc5.
> There was a bug with this that was fixed recently. The patch here
> http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
> t;h=fe655d3a06488c8a188461bca493e9f23fc8c448

Ahh, thanks! :-)
This fix the problem!

>
> >
> >(the intel xeon CPU can work x86-64 kernels?)
> >
>
> Yes. If your CPUs have EM64T capability, then they can run x86-64
> kernels.

OK, i will try it! ;-)

Thanks,
Janos

>
> Thanks,
> Venki
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2005-12-16  8:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 14:00 irq balancing question Pallipadi, Venkatesh
2005-11-17  8:28 ` JaniD++ [this message]
     [not found] <fa.o8VX4Uax4/73QDX3vvhLW5NBvRE@ifi.uio.no>
2007-02-23 14:39 ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2007-02-23 11:32 Imre Gergely
2007-02-23 14:45 ` Arjan van de Ven
2007-02-23 14:58   ` Gergely Imre
2007-02-23 15:54     ` Arjan van de Ven
2007-02-23 18:51       ` Gergely Imre
2007-02-23 19:01         ` Arjan van de Ven
2007-02-23 20:57           ` Gergely Imre
2005-12-15  0:48 Pallipadi, Venkatesh
2005-12-15  9:10 ` JaniD++
2005-12-14 21:05 JaniD++
2005-12-14 21:16 ` Arjan van de Ven
2005-12-14 21:31   ` JaniD++

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='003d01c5eb51$3abb29f0$a700a8c0@dcccs' \
    --to=djani22@dynamicweb.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).