From: Karsten Keil <kkeil@suse.de>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: kai.germaschewski@gmx.de, isdn4linux@listserv.isdn4linux.de,
linux-kernel@vger.kernel.org
Subject: Re: [STACK] weird code in some isdn drivers
Date: Wed, 9 Jun 2004 15:16:28 +0200 [thread overview]
Message-ID: <20040609131628.GA10403@pingi3.kke.suse.de> (raw)
In-Reply-To: <20040609123633.GH21168@wohnheim.fh-wedel.de>
On Wed, Jun 09, 2004 at 02:36:33PM +0200, Jörn Engel wrote:
> Karsten, Kai,
>
> while I agree that this is a measurement bug, it's not exacly fun to
> look at the code in question. Can you please find a solution for
> hscx_irq.c?
HiSax and I4L is in bugfix only mode, since it will replaced
by other drivers. So I do not want waste time for soon obsolate code.
>
> Either transform it into a header and uninline some of the longer
> functions or make the functions global and add the necessary header
> and Makefile-line. In any case, I don't like to see something like
> #include "hscx_irq.c"
>
Yes I agree that it looks ugly and make not much more sense with today
CPUs and compilers. In the beginning of the development (on 386/486) and
with early GCC (inline was often broken) it did and reduced some
ping times so far I remember. (~1997)
> stackframes for call path too long (268435490):
> size function
> 0 IsdnCardState->irq_func
> 268435466 teles3_interrupt
> 24 hscx_empty_fifo
> 0 read_fifo
> 0 insb
>
> Jörn
>
> --
> People will accept your ideas much more readily if you tell them
> that Benjamin Franklin said it first.
> -- unknown
--
Karsten Keil
SuSE Labs
ISDN development
next prev parent reply other threads:[~2004-06-09 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:36 Jörn Engel
2004-06-09 13:16 ` Karsten Keil [this message]
2004-06-09 13:30 ` Jörn Engel
2004-06-09 14:16 ` Karsten Keil
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=20040609131628.GA10403@pingi3.kke.suse.de \
--to=kkeil@suse.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kai.germaschewski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®