Re: Interrupt distribution on SMP machine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

On 4/25/07, Muhammad Tayseer Alquoatli <idoit.ief@xxxxxxxxx> wrote:
Hi all:
I'm wondering about interrupts distribution in Linux kernel, lets say
i'm running Linux on a dual core processor, then Linux will distribute
incoming interrupts between these two cores (processors)
lets say also i'm running a service that uses nearly equal
cpu/io/network time like a proxy that has many things to check in the
content before issue an IO command to HDs or to network interface
the question is, is it better to let all IO/network interrupts be
routed to CPU0 and assign CPU1 to run the service user-level process ?
or let Linux handles it if Linux can do it more efficiently

Usually its a good idea to let Linux do it.

and what is the side effect of such partitioning on high IO/network
interrupts on CPU0?
In general, is manual interrupt/cpu assignment on SMP machine a good
or a bad idea?
Thanks in advance

There is an RTOS (RTLinux)  whose basic idea is to let the Linux
kernel handle all non-RT events while another mini-kernel sitting on
top of the vanilla kernel, handles all real time tasks.
So, if such a bifurcation can be handled at the software level to give
"hard" real time performance, it would certainly be very interesting
to do so at the hardware level as well.

Thanks,
Raseel
http://screwgoth.blogspex.com

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux