From: Bill Irwin <bill.irwin@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: bunk@stusta.de, akpm@osdl.org, gcoady@gmail.com, zlynx@acm.org,
dgc@sgi.com, alan@lxorguk.ukuu.org.uk, andi@firstfloor.org,
hch@infradead.org, wli@holomorphy.com, jengelh@linux01.gwdg.de,
bill.irwin@oracle.com, zwane@infradead.org, neilb@suse.de,
jens.axboe@oracle.com, eric@provenscaling.com
Subject: [0/3] i386 stack handling updates
Date: Mon, 30 Apr 2007 16:23:51 -0700 [thread overview]
Message-ID: <20070430232351.GG26598@holomorphy.com> (raw)
This is a series of patches to improve i386 stack handling in several
manners. The net result is to improve system stability via IRQ stacks
while remaining memory efficient and to improve stack debugging.
[1/3] dynamically allocate irq stacks
This conserves memory while using IRQ stacks.
[2/3] make irqstacks unconditional, while retaining 4/8k stack selection
This makes IRQ stacks the standard for mainline.
[3/3] DEBUG_STACK option enabling vmalloc()'ed stacks and __pa checks
Stack debugging option using vmalloc() to establish guard pages.
-- wli
next reply other threads:[~2007-04-30 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 23:23 Bill Irwin [this message]
2007-04-30 23:33 ` [1/3] dynamically allocate IRQ stacks Bill Irwin
2007-04-30 23:37 ` [2/3] unconditional i386 " Bill Irwin
2007-04-30 23:40 ` [3/3] use vmalloc() to arrange guard pages for stacks Bill Irwin
2007-05-01 15:07 ` Chuck Ebbert
2007-05-01 16:31 ` Bill Irwin
2007-05-01 16:40 ` Chuck Ebbert
2007-05-01 16:47 ` Bill Irwin
2007-05-01 17:04 ` [1/3] dynamically allocate IRQ stacks Heiko Carstens
2007-05-01 17:26 ` Bill Irwin
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=20070430232351.GG26598@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=bunk@stusta.de \
--cc=dgc@sgi.com \
--cc=eric@provenscaling.com \
--cc=gcoady@gmail.com \
--cc=hch@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=wli@holomorphy.com \
--cc=zlynx@acm.org \
--cc=zwane@infradead.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