Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: joris lijssens <joris_lijssens1980@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: patch to increase stack size
Date: Fri, 17 Feb 2006 16:04:12 +0000	[thread overview]
Message-ID: <20060217160412.GE18396@linux-mips.org> (raw)
In-Reply-To: <20060216130236.72703.qmail@web36102.mail.mud.yahoo.com>

On Thu, Feb 16, 2006 at 01:02:36PM +0000, joris lijssens wrote:

> I was wondering if there is a patch avaible to
> increase the stack size on a mips 2.6 linux kernel. I
> have found one for the i386 that sets the stack size
> from 4K to 16K. But I don't find anything for the mips
> kernel. I would like it if somebody has some info on
> this topic.

If anything the aim is to shrink the kernel stack further.  The larger
allocations are, then less likely they succeed.

32-bit MIPS kernels use 8kB stack,  64-bit uses 16kB stacks.

  Ralf

      reply	other threads:[~2006-02-17 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 13:02 patch to increase stack size joris lijssens
2006-02-17 16:04 ` Ralf Baechle [this message]

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=20060217160412.GE18396@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=joris_lijssens1980@yahoo.com \
    --cc=linux-mips@linux-mips.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