From: Andi Kleen <andi@firstfloor.org>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Gregory Haskins <gregory.haskins@gmail.com>,
mingo@elte.hu, rostedt@goodmis.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] seqlock: serialize against writers
Date: Fri, 29 Aug 2008 19:08:51 +0200 [thread overview]
Message-ID: <20080829170851.GZ26610@one.firstfloor.org> (raw)
In-Reply-To: <48B826BD.9000308@novell.com>
No idea on the problem itself because I don't understand it, just:
> Given that, we either need to address the const requirement
> for userspace, alter userspace's usage, or find another way to address
> the deadlock. Any ideas?
In the worst case you can always disable the vsyscall gtod() and
thus the need for a user space safe seqlock_t, but it will
hurt some workloads significantly.
-Andi
next prev parent reply other threads:[~2008-08-29 17:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 15:44 Gregory Haskins
2008-08-29 16:09 ` Andi Kleen
2008-08-29 16:10 ` Gregory Haskins
2008-08-29 16:22 ` Andi Kleen
2008-08-29 16:26 ` Gregory Haskins
2008-08-29 16:34 ` Steven Rostedt
2008-08-29 16:35 ` Gregory Haskins
2008-08-29 16:45 ` Andi Kleen
2008-08-29 16:53 ` Steven Rostedt
2008-08-29 17:00 ` Gregory Haskins
2008-08-29 17:00 ` Gregory Haskins
2008-08-29 16:58 ` Steven Rostedt
2008-08-29 16:29 ` Gregory Haskins
2008-08-29 16:37 ` Andi Kleen
2008-08-29 16:41 ` Gregory Haskins
2008-08-29 17:08 ` Andi Kleen [this message]
2008-08-29 16:57 ` Stephen Hemminger
2008-08-29 17:02 ` [ RT PATCH] " Steven Rostedt
2008-08-29 18:03 ` [RT PATCH v2] " Gregory Haskins
2008-08-29 18:12 ` Gregory Haskins
2008-08-30 11:17 ` Peter Zijlstra
2008-08-30 12:32 ` Gregory Haskins
2008-08-30 12:38 ` Peter Zijlstra
2008-08-30 13:05 ` Gregory Haskins
2008-08-30 11:08 ` [PATCH] " Peter Zijlstra
2008-09-02 12:45 ` [RT PATCH v3] " Gregory Haskins
2008-09-02 13:01 ` Gregory Haskins
2008-09-02 13:29 ` [RT PATCH v4] " Gregory Haskins
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=20080829170851.GZ26610@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ghaskins@novell.com \
--cc=gregory.haskins@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®