From: Ingo Molnar <mingo@elte.hu>
To: emin ak <eminak71@gmail.com>
Cc: Kumar Gala <galak@kernel.crashing.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rt10 crash on ppc
Date: Thu, 30 Mar 2006 13:34:52 +0200 [thread overview]
Message-ID: <20060330113452.GA9901@elte.hu> (raw)
In-Reply-To: <2cf1ee820603300225x3c5a6f98qe8bdda1023f0d74f@mail.gmail.com>
* emin ak <eminak71@gmail.com> wrote:
> 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.
well, if SA_INTERRUPT made a difference then you are likely not running
PREEMPT_RT nor PREEMPT_HARDIRQS. Could you send me your .config?
Ingo
next prev parent reply other threads:[~2006-03-30 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 14:56 2.6.16-rt10 crash on ppc emin ak
2006-03-27 17:11 ` emin ak
2006-03-27 20:31 ` emin ak
2006-03-28 1:21 ` Nick Piggin
2006-03-29 15:08 ` Ingo Molnar
2006-03-30 2:55 ` Nick Piggin
2006-03-30 7:13 ` Ingo Molnar
2006-03-30 7:18 ` Kumar Gala
2006-03-30 7:23 ` Ingo Molnar
2006-03-30 10:25 ` emin ak
2006-03-30 11:34 ` Ingo Molnar [this message]
2006-03-30 14:55 ` emin ak
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=20060330113452.GA9901@elte.hu \
--to=mingo@elte.hu \
--cc=eminak71@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.