From: "Manfred Schwarb" <manfred99@gmx.ch>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com, netdev@oss.sgi.com
Subject: Re: 2.4.30-hf1 do_IRQ stack overflows
Date: Thu, 12 May 2005 09:59:50 +0200 (MEST) [thread overview]
Message-ID: <8542.1115884790@www69.gmx.net> (raw)
In-Reply-To: 20050511124640.GE8541@logos.cnet
>
> The traces show huge networking execution paths.
>
> It seems you are using some packet scheduler (CONFIG_NET_SCHED)? Pretty
> much all
> traces show functions from sch_generic.c. Can you disable that for a test?
>
Yes, indeed, I made some experiments with it, but do not need it urgently.
I will disable it, thanks for the hint.
And I will report back.
> >
> > Below my three overflow messages. Would the stack reduction patches of
> Badari Pulavarty
> > help in my case? If so, I would strongly vote for inclusion into 2.4
> series!!
>
> It has been decided that the stack reduction patches were too intrusive to
> be merged
> at this stage of v2.4 life.
>
OK, I got the message, I will consider upgrading to 2.6 sometime this
year...
--
+++ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS +++
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
next prev parent reply other threads:[~2005-05-12 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.2.1.1.2.20050511093252.01c887b0@mail.meteodat.ch>
2005-05-11 12:46 ` 2.4.30-hf1 do_IRQ stack overflows Marcelo Tosatti
2005-05-11 21:38 ` Herbert Xu
2005-05-12 8:44 ` Manfred Schwarb
2005-05-14 11:05 ` Herbert Xu
2005-05-17 16:05 ` Manfred Schwarb
2005-05-12 7:59 ` Manfred Schwarb [this message]
2005-06-07 12:38 ` Manfred Schwarb
2005-06-09 15:00 ` Marcelo Tosatti
2005-06-10 8:10 ` Manfred Schwarb
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=8542.1115884790@www69.gmx.net \
--to=manfred99@gmx.ch \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.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).