From: Arjan van de Ven <arjanv@redhat.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] larger kernel stack (8k->16k) per task
Date: Fri, 08 Feb 2002 15:36:31 +0000 [thread overview]
Message-ID: <3C63F07F.323A32DE@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202081511400.1359-100000@einstein.homenet>
Tigran Aivazian wrote:
>
> Hi,
>
> In the light of some talks here about increasing kernel stack, here is my
> patch for i386 architecture that some may find useful. It also has a nice
> extra (/proc/stack) implemented by Hugh Dickins which helps to find major
> offenders.
>
> It is against 2.4.9 but should be easy to port in any direction. (One way
> the patch could be improved is by making the size CONFIG_ option instead
> of hardcoding). Oh btw, please don't tell me "but now you'd need _four_
> physically-contiguous pages to create a task instead of two!" because I
> know it (and think it's not too bad).
I do think it is too bad. Sorry.
Also it's the wrong approach. The right approach (as done by Manfred and
David) is
to put "current" no longer on this stack just a pointer to current.
And .... if you need a 16Kb stack your kernel code is VERY VERY sick.
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2002-02-08 15:37 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 [this message]
2002-02-08 15:43 ` Rik van Riel
2002-02-08 15:52 ` Alan Cox
2002-02-08 20:08 ` Andrew Morton
-- 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=3C63F07F.323A32DE@redhat.com \
--to=arjanv@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox