From: Peter Zijlstra <peterz@infradead.org>
To: Robin Holt <holt@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
ptesarik@suse.cz, tee@sgi.com, mingo@elte.hu,
linux-arch@vger.kernel.org
Subject: Re: [Patch V3 0/3] Enable irqs when waiting for rwlocks
Date: Wed, 03 Dec 2008 13:25:17 +0100 [thread overview]
Message-ID: <1228307117.9673.232.camel@twins> (raw)
In-Reply-To: <20081203113744.GE8970@sgi.com>
On Wed, 2008-12-03 at 05:37 -0600, Robin Holt wrote:
> > It's a bit regrettable to have different architectures behaving in
> > different ways. It would be interesting to toss an x86_64
> > implementation into the grinder, see if it causes any problems, see if
> > it produces any tangible benefits. Then other architectures might
> > follow. Or not, depending on the results ;)
>
> I personally expect SGI to work on this for x86_64 in the future.
> Once we actually start testing systems with 128 and above cpus, I
> would expect to see these performance issues needing to be addressed.
> Until then, it is just a theoretical.
Personally I consider this a ugly hack and would love to see people
solve the actual problem and move away from rwlock_t, its utter rubbish.
next prev parent reply other threads:[~2008-12-03 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081104122405.046233722@attica.americas.sgi.com>
2008-12-03 0:13 ` [Patch V3 0/3] Enable irqs when waiting for rwlocks Andrew Morton
2008-12-03 0:13 ` Andrew Morton
2008-12-03 11:37 ` Robin Holt
2008-12-03 12:25 ` Peter Zijlstra [this message]
2008-12-03 12:36 ` Petr Tesarik
2008-12-03 12:36 ` Petr Tesarik
2008-12-03 12:44 ` Peter Zijlstra
2008-12-03 12:44 ` Peter Zijlstra
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=1228307117.9673.232.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=holt@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ptesarik@suse.cz \
--cc=tee@sgi.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