mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	"Dave Jones" <davej@redhat.com>, "Chris Mason" <mason@suse.com>,
	reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [STACK] >3k call path in reiserfs
Date: Fri, 11 Jun 2004 09:03:57 +0200	[thread overview]
Message-ID: <1086937437.2731.11.camel@laptop.fenrus.com> (raw)
In-Reply-To: <40C91DA0.6060705@namesys.com>

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

On Fri, 2004-06-11 at 04:49, Hans Reiser wrote:
> >
> I have a concept of stable version and development version.  V3 is the 
> stable release branch, and should not be disturbed except for bug 
> fixes.  

Hans,

I would call stack use like this a bug fix. Let me explain why: in the
2.4 kernel you ALREADY have effectively a 4Kb stack (it's 8Kb but when
you subtract 1.6Kb for the task struct and about 2Kb for soft/hardirq
context about 4Kb is left). It's just more of a lottery there about
if/when you get hit by an irq or not, while with 4KSTACKS in 2.6 the
odds of the lottery changed. I'm sure that as maintainer of a filesystem
that, as you say, is critical and holds peoples email an other critical
data, you rather not play odds at all, regardless of what they are, and
want to play for certainty.

Greetings,
     Arjan van de Ven

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-11  8:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 12:22 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
2004-06-10 22:35               ` Jörn Engel
2004-06-11  2:49                 ` Hans Reiser
2004-06-11  7:03                   ` Arjan van de Ven [this message]
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=1086937437.2731.11.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=davej@redhat.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiser@namesys.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 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®