From: Petr Tesarik <ptesarik@suse.cz>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Robin Holt <holt@sgi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: RE: [PATCH V2 0/2] enable irqs when waiting for rwlocks
Date: Wed, 05 Nov 2008 09:54:33 +0000 [thread overview]
Message-ID: <1225878873.3033.1.camel@elijah.suse.cz> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA35BE0554D@orsmsx505.amr.corp.intel.com>
On Mon, 2008-11-03 at 13:47 -0800, Luck, Tony wrote:
> > Just a few years of experiencal evidence. The equivalent of this patch
> > has been in the SuSE SLES10 kernel for years and not been detected as
> > being negative.
>
> That's good to know.
>
> Petr: I tried to apply these ... but the patches seem corrupted
> (leading spaces dropped? ... I checked in the marc.info archive
> and they seem broken there too). Can you regenerate them and
> repost (attachments are ok).
Oops. Interesting.
Anyway, I can see that Robin Holt has already regenerated the patches
against the latest directory structure, so I assume there's nothing more
to be done.
Petr
prev parent reply other threads:[~2008-11-05 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 15:57 [PATCH V2 0/2] enable irqs when waiting for rwlocks Petr Tesarik
2008-10-23 16:06 ` [PATCH V2 1/3] Factor out #ifdef's from kernel/spinlock.c to Petr Tesarik
2008-11-27 15:32 ` Peter Zijlstra
2008-10-23 16:06 ` [PATCH V2 2/3] Allow rwlocks to re-enable interrupts Petr Tesarik
2008-11-27 15:33 ` Peter Zijlstra
2008-10-31 8:52 ` [PATCH V2 0/2] enable irqs when waiting for rwlocks Petr Tesarik
2008-10-31 20:22 ` Luck, Tony
2008-11-03 11:46 ` Robin Holt
2008-11-03 21:47 ` Luck, Tony
2008-11-05 9:54 ` Petr Tesarik [this message]
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=1225878873.3033.1.camel@elijah.suse.cz \
--to=ptesarik@suse.cz \
--cc=holt@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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