From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: gcoady@gmail.com
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 4k stacks
Date: Fri, 23 Dec 2005 17:45:41 +0000 [thread overview]
Message-ID: <200512231745.41400.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <pfjmq1dtcrq5hos687h0gm9nrg79v3ceat@4ax.com>
On Friday 23 December 2005 01:11, Grant Coady wrote:
> On Thu, 22 Dec 2005 16:53:25 -0500, "linux-os \(Dick Johnson\)"
<linux-os@analogic.com> wrote:
> >Yesterday I sent a patch to add stack-poison so the stack usage
> >could be observed.
> >
> >Today I wrote a small program and tested the stack usage. Both
> >the program and the patch is attached. The result is:
> >
> >Offset : 2ec8f000 Available Stack bytes = 3104
> >Offset : 2ecb1000 Available Stack bytes = 3104
> >Offset : 2ee5f000 Available Stack bytes = 20
>
> Hmm:
> # ./stack
> Offset : 003fb000 Available Stack bytes = 3348
> Offset : 0195d000 Available Stack bytes = 3620
Please do these tests once you repair the bug preventing the 4K stacks kernel
from booting. The results are meaningless on an 8K stacks kernel.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2005-12-23 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 21:53 linux-os (Dick Johnson)
2005-12-23 1:11 ` Grant Coady
2005-12-23 17:45 ` Alistair John Strachan [this message]
2005-12-23 12:56 ` Krzysztof Halasa
2005-12-24 12:03 ` Denis Vlasenko
2005-12-25 2:43 ` Andrew James Wade
2005-12-26 7:42 ` Andrew James Wade
2005-12-26 8:40 ` Andrew James Wade
2005-12-27 21:12 ` Frank Sorenson
2005-12-28 18:05 ` Grant Coady
2005-12-26 14:38 ` Diego Calleja
2005-12-28 13:14 ` linux-os (Dick Johnson)
2005-12-28 15:16 ` Denis Vlasenko
2005-12-30 14:45 ` linux-os (Dick Johnson)
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=200512231745.41400.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=gcoady@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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®