From: ebiederm@xmission.com (Eric W. Biederman)
To: Avi Kivity <avi@argo.co.il>
Cc: Bill Irwin <bill.irwin@oracle.com>,
Arjan van de Ven <arjan@infradead.org>,
Hugh Dickins <hugh@veritas.com>,
Chuck Ebbert <cebbert@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: simple, safe x86 stack overflow detection
Date: Mon, 19 Mar 2007 14:53:22 -0600 [thread overview]
Message-ID: <m1k5xdvttp.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <45EFBEB3.20708@argo.co.il> (Avi Kivity's message of "Thu, 08 Mar 2007 09:43:47 +0200")
Avi Kivity <avi@argo.co.il> writes:
> I don't understand why interrupt latency suffers. Sure, the interrupt that's
> being masked is delayed, but on the other hand the interrupt that's doing the
> masking is not. We're moving the latency from the first interrupt to the
> second, probably with a slight gain in overall throughput.
>
> It *does* matter if the interrupts have meaningful priorities. Is that the case
> here?
No.
I'll queue this in my irq things to think about...
Eric
next prev parent reply other threads:[~2007-03-19 20:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 14:27 Wanted: simple, safe x86 stack overflow detection Chuck Ebbert
2007-02-28 16:31 ` Thiago Galesi
2007-02-28 20:41 ` Andi Kleen
2007-02-28 23:20 ` Bill Irwin
2007-02-28 23:36 ` Jan Engelhardt
2007-02-28 23:45 ` Bill Irwin
2007-03-04 1:50 ` Bill Irwin
2007-03-06 18:59 ` Chuck Ebbert
2007-03-06 19:43 ` Hugh Dickins
2007-03-06 20:34 ` Bill Irwin
2007-03-07 4:28 ` Arjan van de Ven
2007-03-07 6:44 ` Bill Irwin
2007-03-07 12:34 ` Arjan van de Ven
2007-03-07 14:48 ` Bill Irwin
2007-03-07 15:04 ` Arjan van de Ven
2007-03-08 7:43 ` Avi Kivity
2007-03-19 20:53 ` Eric W. Biederman [this message]
2007-03-06 20:06 ` Bill Irwin
2007-03-05 1:18 ` Arnd Bergmann
2007-03-05 12:39 ` Andi Kleen
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=m1k5xdvttp.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=avi@argo.co.il \
--cc=bill.irwin@oracle.com \
--cc=cebbert@redhat.com \
--cc=hugh@veritas.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox