All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: benh@kernel.crashing.org
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] (0/4) stack updates for x86
Date: Mon, 09 Dec 2002 14:09:01 -0800	[thread overview]
Message-ID: <3DF5147D.9060708@us.ibm.com> (raw)

The kernel currently uses an 8k stack, per task.  Here is the 
infrastructure needed to allow us to halve that.  The original work 
was by Ben LaHaise.  I broke it out into several patches and updated 
it for the current kernels.

A-thread_info_cleanup-2.5.50+bk-5.patch
	Gets asm-i386/thread_info.h ready for the irqstack and
	overflow detection patches

B-interrupt_stacks-2.5.50+bk-5.patch
	Have special stacks for use in interrupts.

C-stack_usage_check-2.5.50+bk-5.patch
	Check for stack overflows on entry to each funtion.  Use gcc's
	-p profiling feature to do it.

D-4k-stack-2.5.50+bk-5.patch
	make a config option to turn on 4k stacks.  (there appears to
	be a problem with this right now).

-- 
Dave Hansen
haveblue@us.ibm.com


                 reply	other threads:[~2002-12-09 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3DF5147D.9060708@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=arjanv@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.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 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.