From: Andi Kleen <andi@firstfloor.org>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: Jeff Layton <jlayton@poochiereds.net>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
John Kacur <jkacur@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [RFC v1 0/5] fs/locks: Use plain percpu spinlocks instead of lglock to protect file_lock
Date: Fri, 20 Feb 2015 08:05:52 -0800 [thread overview]
Message-ID: <87vbiwwotb.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1424443195-18676-1-git-send-email-daniel.wagner@bmw-carit.de> (Daniel Wagner's message of "Fri, 20 Feb 2015 15:39:50 +0100")
Daniel Wagner <daniel.wagner@bmw-carit.de> writes:
>
> I am looking at how to get rid of lglock. Reason being -rt is not too
> happy with that lock, especially that it uses arch_spinlock_t and
AFAIK it could just use normal spinlock. Have you tried that?
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-02-20 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 14:39 [RFC v1 0/5] fs/locks: Use plain percpu spinlocks instead of lglock to protect file_lock Daniel Wagner
2015-02-20 14:39 ` [RFC v1 1/5] locks: Remove unnecessary IS_POSIX test Daniel Wagner
2015-02-20 14:39 ` [RFC v1 2/5] locks: Split insert/delete block functions into flock/posix parts Daniel Wagner
2015-02-20 14:39 ` [RFC v1 3/5] seq_file: Add percpu seq_hlist helpers with locking iterators Daniel Wagner
2015-02-20 14:39 ` [RFC v1 4/5] locks: Use percpu spinlocks to protect file_lock_list Daniel Wagner
2015-02-20 14:39 ` [RFC v1 5/5] locks: Use blocked_lock_lock only to protect blocked_hash Daniel Wagner
2015-02-20 16:05 ` Andi Kleen [this message]
2015-02-24 15:58 ` [RFC v1 0/5] fs/locks: Use plain percpu spinlocks instead of lglock to protect file_lock Daniel Wagner
2015-02-24 21:06 ` Jeff Layton
2015-02-27 15:01 ` Daniel Wagner
2015-02-27 15:30 ` Jeff Layton
2015-03-02 12:58 ` Daniel Wagner
2015-03-03 0:29 ` Jeff Layton
2015-03-04 14:03 ` Daniel Wagner
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=87vbiwwotb.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=bfields@fieldses.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=jkacur@redhat.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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