From: Hans Reiser <reiser@namesys.com>
To: Dave Jones <davej@redhat.com>
Cc: "Chris Mason" <mason@suse.com>,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [STACK] >3k call path in reiserfs
Date: Wed, 09 Jun 2004 16:40:18 -0700 [thread overview]
Message-ID: <40C79FE2.4040802@namesys.com> (raw)
In-Reply-To: <20040609182037.GA12771@redhat.com>
Dave Jones wrote:
>On Wed, Jun 09, 2004 at 11:04:49AM -0700, Hans Reiser wrote:
> > >>Can you give me some background on whether this is causing real problems
> > >>for real users?
> > >
> > >Especially with the 4k stack option enabled, it will cause real problems
> > >for real users. A better change would be to cut down on the size of the
> > >tree balance struct, but that would be more invasive. For starters we
> > >might be able to switch from ints to shorts for some of the arrays.
> > >
> > >-chris
> > >
> > Can you tell me about the "4k stack option"?
>
>Arjan's original patch & announcement are at
>http://people.redhat.com/arjanv/4kstack.patch
>
> Dave
>
>
>
>
>
Forcing kernel developers to distort their coding to keep stack sizes
small is not a good idea, as it makes the whole kernel harder to code
for a not very compelling (for 99% of users, please argue with me if you
think it is otherwise) benefit.
I do not think I favor disturbing V3's stability for the sake of the 4k
stack option, but my mind is still open.
next prev parent reply other threads:[~2004-06-09 23:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:22 [STACK] >3k call path in reiserfs Jörn Engel
2004-06-09 12:31 ` Chris Mason
2004-06-09 16:53 ` Chris Mason
2004-06-09 17:06 ` Hans Reiser
2004-06-09 17:15 ` Chris Mason
2004-06-09 18:04 ` Hans Reiser
2004-06-09 18:20 ` Dave Jones
2004-06-09 23:40 ` Hans Reiser [this message]
2004-06-10 22:35 ` Jörn Engel
2004-06-11 2:49 ` Hans Reiser
2004-06-11 7:03 ` Arjan van de Ven
2004-06-11 13:46 ` Jörn Engel
2004-06-11 16:32 ` Hans Reiser
2004-06-11 16:50 ` Jörn Engel
2004-06-11 17:08 ` Paul Wagland
2004-06-11 17:46 ` Chris Mason
2004-06-11 18:07 ` Hans Reiser
2004-06-11 14:31 ` Timothy Miller
2004-06-11 14:42 ` Jörn Engel
2004-06-09 17:28 ` Jörn Engel
2004-06-09 18:09 ` Hans Reiser
2004-06-09 18:34 ` Jörn Engel
2004-06-09 23:42 ` Hans Reiser
2004-06-11 13:49 ` Jörn Engel
2004-06-11 16:34 ` Hans Reiser
2004-06-09 18:48 ` Chris Mason
2004-06-09 18:53 ` Jörn Engel
2004-06-09 23:44 ` Hans Reiser
2004-06-10 9:08 ` Vladimir Saveliev
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=40C79FE2.4040802@namesys.com \
--to=reiser@namesys.com \
--cc=davej@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-dev@namesys.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 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.