All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>
Subject: Re: [patch] larger kernel stack (8k->16k) per task
Date: Fri, 08 Feb 2002 12:08:42 -0800	[thread overview]
Message-ID: <3C64304A.35BA9E47@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0202081511400.1359-100000@einstein.homenet>

Tigran Aivazian wrote:
> 
> ...
> +               memset((char*)tsk+sizeof(struct task_struct), 0,        \
> +                       THREAD_SIZE-sizeof(struct task_struct));        \
> +       }                                                               \

This seems to be permanently enabled?  If so, I'd suggest that it
be made conditional on CONFIG_SLAB_DEBUG, or such.

> ...
> -# define INIT_TASK_SIZE        2048*sizeof(long)
> +# define INIT_TASK_SIZE        4096*sizeof(long)

Personally, I'd rather we make the stack 4k for a while,
and fix the resulting mess.

-

  parent reply	other threads:[~2002-02-08 20:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08 15:20 [patch] larger kernel stack (8k->16k) per task Tigran Aivazian
2002-02-08 15:36 ` Arjan van de Ven
2002-02-08 15:43 ` Rik van Riel
2002-02-08 15:52 ` Alan Cox
2002-02-08 20:08 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-08 16:06 Tigran Aivazian
2002-02-08 16:09 ` Arjan van de Ven
2002-02-08 16:59   ` Tigran Aivazian
2002-02-08 16:57     ` Arjan van de Ven
2002-02-08 17:23     ` Arjan van de Ven
2002-02-08 18:16       ` Alan Cox
2002-02-08 18:29       ` Richard B. Johnson
2002-02-08 18:38         ` Arjan van de Ven
2002-02-08 20:54         ` Ingo Molnar
2002-02-08 18:15     ` Alan Cox
2002-02-08 20:22     ` Jes Sorensen
2002-02-08 21:12       ` Mike Fedyk
2002-02-09  7:17         ` george anzinger

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=3C64304A.35BA9E47@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@veritas.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.