From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Clark Williams <williams@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Kleen, Andi" <andi.kleen@intel.com>
Subject: Re: [RFC][PATCH] x86: Lazy disabling of interrupts
Date: Wed, 09 Oct 2013 13:45:50 -0700 [thread overview]
Message-ID: <5255C07E.70805@linux.intel.com> (raw)
In-Reply-To: <20131009144150.108f7041@gandalf.local.home>
> Summary
> -------
>
> Although the extreme case shows a nice improvement, I'm skeptical if it
> is worth doing for real world applications.
You did the experiment, and credit to you for not going "I did the work,
now include it" but rather for publishing the results so we can learn
from them.
It *does* make me wonder if we can leverage RTM for a significant subset
of these (as an interrupt will abort a transaction); that should be
substantially cheaper and less complex.
-hpa
next parent reply other threads:[~2013-10-09 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131009144150.108f7041@gandalf.local.home>
2013-10-09 20:45 ` H. Peter Anvin [this message]
2013-10-09 22:25 ` [RFC][PATCH] x86: Lazy disabling of interrupts Andi Kleen
2013-10-10 0:36 ` Steven Rostedt
2013-10-10 3:39 ` David Miller
2013-10-10 3:54 ` Steven Rostedt
2013-10-10 4:53 ` Ingo Molnar
[not found] ` <20131010001153.1f171bff@gandalf.local.home>
2013-10-10 4:19 ` David Miller
2013-10-10 9:03 ` Borislav Petkov
2013-10-10 12:30 ` Steven Rostedt
2013-10-10 13:40 ` Borislav Petkov
2013-10-10 12:27 Steven Rostedt <rostedt@goodmis.org> (by way of Steven Rostedt <rostedt@goodmis.org>) (by way of Steven Rostedt
2013-10-10 14:45 ` anish singh
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=5255C07E.70805@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=williams@redhat.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