From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Andrea Arcangeli <andrea@suse.de>,
arjanv@redhat.com, Chris Wedgwood <cw@f00f.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/3] Separate IRQ-stacks from 4K-stacks option
Date: Fri, 10 Sep 2004 16:12:05 +0100 [thread overview]
Message-ID: <1094829125.17464.14.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0409101555510.16784-100000@localhost.localdomain>
On Gwe, 2004-09-10 at 16:07, Hugh Dickins wrote:
> Chris's patch seems eminently sensible to me. Why should having separate
> interrupt stack depend on whether you're configured for 4K or 8K stacks?
You only have 4K safe to use in all current configurations. Its a case
of simply fixing the sloppy code (and or pushing up compiler versions
where the compiler is the offender).
> Wasn't Andrea worried, a couple of months back, about nested interrupts
> overflowing the 4K interrupt stack?
We've seen no evidence of this and assuming apps could use 4K safely the
interrupt "stack" was about 2.5K before. Limiting it either by size or
by depth is not a big problem at all.
next prev parent reply other threads:[~2004-09-10 16:16 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 23:25 [PATCH 1/3] Separate IRQ-stacks from 4K-stacks option Chris Wedgwood
2004-09-09 23:55 ` Brian Gerst
2004-09-09 23:59 ` Chris Wedgwood
2004-09-10 6:40 ` Arjan van de Ven
2004-09-10 6:45 ` Chris Wedgwood
2004-09-10 6:52 ` Arjan van de Ven
2004-09-10 7:15 ` Chris Wedgwood
2004-09-10 7:21 ` Arjan van de Ven
2004-09-10 7:23 ` Chris Wedgwood
2004-09-10 7:35 ` Arjan van de Ven
2004-09-10 9:12 ` Alan Cox
2004-09-10 9:14 ` Alan Cox
2004-09-10 10:27 ` Russell King
2004-09-10 14:30 ` Martin J. Bligh
2004-09-10 15:06 ` Chris Wedgwood
2004-09-10 15:07 ` Hugh Dickins
2004-09-10 15:12 ` Alan Cox [this message]
2004-09-10 15:15 ` Arjan van de Ven
2004-09-10 15:28 ` Andrea Arcangeli
2004-09-10 15:09 ` Alan Cox
2004-09-10 15:34 ` Arjan van de Ven
2004-09-12 14:17 ` Andrea Arcangeli
2004-09-12 15:03 ` Martin J. Bligh
2004-09-12 15:45 ` Zwane Mwaikambo
2004-09-12 16:00 ` Martin J. Bligh
2004-10-20 16:27 ` Lee Revell
2004-10-21 15:18 ` Zwane Mwaikambo
2004-09-12 19:18 ` Lee Revell
2004-09-12 19:25 ` Chris Wedgwood
2004-09-12 19:35 ` Ingo Molnar
2004-09-12 19:40 ` Chris Wedgwood
2004-09-12 19:44 ` Ingo Molnar
2004-09-12 20:33 ` Andrea Arcangeli
2004-09-12 21:36 ` Lee Revell
2004-09-12 22:07 ` Andrea Arcangeli
2004-09-12 22:25 ` Lee Revell
2004-09-13 6:16 ` Ingo Molnar
2004-09-13 7:27 ` Lee Revell
2004-09-15 19:43 ` Bill Davidsen
2004-09-15 19:51 ` Andrea Arcangeli
2004-09-15 20:00 ` Ingo Molnar
2004-09-15 20:39 ` Lee Revell
2004-10-20 17:50 ` Timothy Miller
2004-09-13 7:32 ` Jens Axboe
2004-09-13 10:31 ` Andrea Arcangeli
2004-09-13 10:34 ` Arjan van de Ven
2004-09-13 12:30 ` Jens Axboe
2004-10-20 17:46 ` Timothy Miller
2004-09-13 10:51 ` Alan Cox
2004-09-13 20:26 ` Bill Davidsen
2004-09-14 5:20 ` Lee Revell
2004-10-20 15:46 ` Timothy Miller
2004-10-20 15:35 ` Arjan van de Ven
2004-10-20 16:39 ` Lee Revell
2004-10-20 16:50 ` Andrea Arcangeli
2004-10-20 16:55 ` Lee Revell
2004-10-20 17:08 ` Andrea Arcangeli
2004-10-20 17:15 ` Lee Revell
2004-10-20 17:34 ` Andrea Arcangeli
2004-10-20 17:58 ` Timothy Miller
2004-10-20 17:55 ` Lee Revell
2004-10-20 18:25 ` Timothy Miller
2004-10-20 18:28 ` Lee Revell
2004-10-20 18:51 ` Alan Cox
2004-10-20 23:19 ` Lee Revell
2004-09-10 15:16 ` Martin J. Bligh
2004-10-20 15:43 ` Timothy Miller
2004-10-20 15:35 ` Arjan van de Ven
2004-09-10 15:58 ` Alexander E. Patrakov
2004-09-10 16:19 ` Nathan Bryant
2004-09-10 17:54 ` Martin J. Bligh
2004-09-10 17:54 ` Bill Davidsen
2004-09-10 9:27 ` Alan Cox
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=1094829125.17464.14.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=arjanv@redhat.com \
--cc=cw@f00f.org \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 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.