From: Peter Zijlstra <peterz@infradead.org>
To: Andreas Mohr <andi@lisas.de>
Cc: der.herr@hofr.at, Al Viro <viro@ZenIV.linux.org.uk>,
mingo@redhat.com, torvalds@linux-foundation.org,
dave@stgolabs.net, Oleg Nesterov <oleg@redhat.com>,
riel@redhat.com, tj@kernel.org, paulmck@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] fs/locks: Replace lg_global with a percpu-rwsem
Date: Tue, 6 Sep 2016 10:59:42 +0200 [thread overview]
Message-ID: <20160906085942.GH10153@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160906083601.GA4964@rhlx01.hs-esslingen.de>
On Tue, Sep 06, 2016 at 10:36:01AM +0200, Andreas Mohr wrote:
> There might be further archives (other than gmane.org or some such),
> however so far lkml.org seemed to be quite ok
> and with IMHO better usability than some others
Agreed, in that I liked the interface best too, however:
> (although it has degraded a lot indeed in recent times,
> judging from
> many server/connection issues and
> not listing details any more due to SPAM etc.).
this has gotten to the point where it often simply doesn't show messages
anymore, threads are incomplete etc..
> > > A possibly good way to commit-micro-manage this would be:
> > > 1. commit shoves things into a newly created encapsulation/wrapper helper
> > > stuff_lock(&flc_lock); /* <---- naming surely can be improved here */
> >
> > No, because not all instances of flc_flock need the percpu-rwsem held,
> > creating such a wrapper could mistakenly create the impression it
> > should.
>
> OK, that aspect sounds valid.
> However with a helper appropriately named to be focussing on
> that use case (protecting that section communication),
> it might be less of a concern.
Dunno, I'd struggling to come up with a sensible name for such a
construct. I'll leave that to others. If it really is desired we can
always do so later.
next prev parent reply other threads:[~2016-09-06 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 1:58 [PATCH 2/7] fs/locks: Replace lg_global with a percpu-rwsem Andreas Mohr
2016-09-06 8:23 ` Peter Zijlstra
2016-09-06 8:36 ` Andreas Mohr
2016-09-06 8:59 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-05 19:40 [PATCH 0/7] perpcu rwsem, fs/locks and killing lglocks Peter Zijlstra
2016-09-05 19:40 ` [PATCH 2/7] fs/locks: Replace lg_global with a percpu-rwsem 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=20160906085942.GH10153@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi@lisas.de \
--cc=dave@stgolabs.net \
--cc=der.herr@hofr.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).