interrupt routing -- moving to acpi@
_pppp at mail.ru
Thu Feb 10 06:35:55 PST 2005
Thanks to all who tried to help. I decided to move the discussion to acpi@
> >>> Ah, so they are all on the same bus. Yuck, performance is going to be
> >>> sucky. Bad Tyan, no cookie. That'll also explain the limited number of
> >>> interrupts available. I don't think there's anything we can do to help
> >>> the situation, sadly.
> >> I cannot affect the company equipment purchase policy either :/
> >> 2 more servers on Tyan motherboards perform pretty bad also.
> > Well this IS PC hardware we're talkinga bout here. :)
> > If you can show that some other OS is able to confgiure an alternate
> > interrupt then it might just be something up with ACPI.
> I actually want the NICs and SCSI controllers run in different kernel threads.
> I have found a year-old discussion on -current
> about assigning physical IRQ lines to PCI devices;
> so I wanted to know if there is a way to force ACPI assign virtual interrupts a similar way.
> I hope I would have some vacant time this weekend to dig in the ACPI code a bit; I think it is not natural to assign a virtual IRQ for 2 devices if there are a plenty of free lines left...
> >> Well, I dont experience any problems with the base system (the server
> >> has 4G of physical RAM btw). The ports collection isnt amd64-ready
> >> though. I compiled some ports patching their makefiles but some of them
> >> dont compile at all. Say, I failed to build vnc server from ports (I
> >> needed it to install Oracle) the only one I managed to build was an
> >> ancient realvnc (3.3.7), but I couldnt connect to it. I tried to compile
> >> realvnc 4.x from sources but ran into namespace issues (they were
> >> discussed on another thread here regarding some software package; seems
> >> to be a buggy gcc). So, Ive given up and happily installed an i386
> >> version.
> > Well, thats not a failing of the ports system itself :-) Did you report
> > your problems to the port maintainers?
> Some of them before I have given up...
> freebsd-stable at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
More information about the freebsd-stable