From: Denys Vlasenko <vda.linux@googlemail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: Re: 4KSTACKS + DEBUG_STACKOVERFLOW harmful
Date: Fri, 31 Aug 2007 12:11:25 +0100 [thread overview]
Message-ID: <200708311211.25143.vda.linux@googlemail.com> (raw)
In-Reply-To: <46D5F462.9010401@redhat.com>
On Wednesday 29 August 2007 23:34, Eric Sandeen wrote:
> Noticed today that the combination of 4KSTACKS and DEBUG_STACKOVERFLOW
> config options is a bit deadly.
>
> DEBUG_STACKOVERFLOW warns in do_IRQ if we're within THREAD_SIZE/8 of the
> end of useable stack space, or 512 bytes on a 4k stack.
...
> The large stack usage in those 2 functions is due to big char arrays, of
> size KSYM_NAME_LEN (128 bytes) and KSYM_SYMBOL_LEN (223 bytes).
>
> IOW, the stack warning effectively reduces useful stack left in our itty
> bitty 4k stacks by over 10%.
KSYM_NAME_LEN = 128 sounds stupid. The name which is wider than 80 chars??
Kernel shouldn't have names that long.
Say, 50 chars ought to be enough.
--
vda
next prev parent reply other threads:[~2007-08-31 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 22:34 4KSTACKS + DEBUG_STACKOVERFLOW harmful Eric Sandeen
2007-08-29 22:53 ` Jesper Juhl
2007-08-29 23:01 ` Eric Sandeen
2007-08-29 23:55 ` Kyle Moffett
2007-08-31 11:11 ` Denys Vlasenko [this message]
2007-08-31 14:35 ` Jörn Engel
2007-08-31 17:16 ` Denys Vlasenko
2008-05-28 14:36 ` Mike Snitzer
2008-05-28 15:13 ` Eric Sandeen
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=200708311211.25143.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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