Re: 2.6.16-rt10 crash on ppc

["emin ak" <eminak71@gmail.com>]

Soryy fot the late answer. I have change the driver to use
SA_INTERRUPT, OOM messages disappeared but the ethernet
throughput decreased significantly as Kumar said before(90MBit for
1518Byte packet, and throughput without the patch is
about 900Bits) and the system can't manage load
balancing between to interfaces,the system acts like
the priorty of tsec0 (eth0) is higher then tsec1 because of
this, under heavy load on tsec0 blocks packet receiving
on tsec1 (eth1). And also I have tried Nick solution, increased
/proc/sys/vm/min_free_kbytes to 10MB, the result did'nt changed, OOM
messages was repeated again.
I'll try Ingo patch immediately and and report you the results.
Thanks.
Emin


2006/3/30, Ingo Molnar <mingo@elte.hu>:
>
> * Kumar Gala <galak@kernel.crashing.org> wrote:
>
> > The issue me actually be a driver interrupt locking bug.  The driver
> > supports three distinct interrupts for TX, RX, Error.  I asked Emin to
> > try changing the driver to use SA_INTERRUPT in the request_irq() to
> > see what happens.  I believe that when he did that it worked but hurts
> > performance.
>
> this is the -rt kernel, with PREEMPT_RT enabled, so SA_INTERRUPT should
> make no difference. All interrupts are executed by their interrupt
> thread, and are fully preemptible:
>
> fastcall int handle_IRQ_event(unsigned int irq, struct pt_regs *regs,
>                                struct irqaction *action)
> {
>        int ret, retval = 0, status = 0;
>
>        /*
>         * Unconditionally enable interrupts for threaded
>         * IRQ handlers:
>         */
>        if (!hardirq_count() || !(action->flags & SA_INTERRUPT))
>                local_irq_enable();
>
> i.e. SA_INTERRUPT should have no effect.
>
>        Ingo
>