From: Matthew Wilcox <willy@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
xfs <linux-xfs@vger.kernel.org>,
Ilya Dryomov <idryomov@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Brian Foster <bfoster@redhat.com>,
holger@applied-asynchrony.com,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] iomap: report collisions between directio and buffered writes to userspace
Date: Tue, 21 Nov 2017 04:52:53 -0800 [thread overview]
Message-ID: <20171121125253.GA1484@bombadil.infradead.org> (raw)
In-Reply-To: <20171121064815.GP5858@dastard>
On Tue, Nov 21, 2017 at 05:48:15PM +1100, Dave Chinner wrote:
> On Mon, Nov 20, 2017 at 08:32:40PM -0800, Matthew Wilcox wrote:
> > On Mon, Nov 20, 2017 at 05:37:53PM -0800, Darrick J. Wong wrote:
> > > On Tue, Nov 21, 2017 at 09:27:49AM +1100, Dave Chinner wrote:
> > > > First thing I noticed was that "xa" as a prefix is already quite
> > > > widely used in XFS - it's shorthand for "XFS AIL". Indeed, xa_lock
> >
> > The X stands for 'eXpandable' or 'eXtending'. I really don't want to
> > use more than a two-letter acronym for whatever the XArray ends up being
> > called. One of the problems with the radix tree is that everything has
> > that 11-character 'radix_tree_' prefix; just replacing that with 'xa_'
> > makes a huge improvement to readability.
>
> Yeah, understood. That's why
> we have very little clear
> prefix namespace left.... :/
>
> [ somedays I write something that looks sorta like a haiku, and from
> that point on everything just starts falling out of my brain that
> way. I blame Eric for this today! :P ]
When the namespace is
tight we must consider the
competing users.
The earliest us'r
has a claim to a prefix
we are used to it.
Also a more wide-
spread user has a claim to
a shorter prefix.
Would you mind changing
your prefix to one only
one letter longer?
... ok, I give up ;-)
All your current usage of the xa_ prefix looks somewhat like this:
fs/xfs/xfs_trans_ail.c: spin_lock(&ailp->xa_lock);
with honourable mentions to:
fs/xfs/xfs_log.c: spin_lock(&mp->m_ail->xa_lock);
Would you mind if I bolt a patch on to the front of the series called
something like "free up xa_ namespace" that renamed your xa_* to ail_*?
There are no uses of the 'ail_' prefix in the kernel today.
I don't think that
spin_lock(&ailp->ail_lock);
loses any readability.
By the way, what does AIL stand for? It'd be nice if it were spelled out
in at least one of the header files, maybe fs/xfs/xfs_trans_priv.h?
> Zoetrope Array.
> Labyrinth of illusion.
> Structure never ends.
Thank you for making me look up zoetrope ;-)
next prev parent reply other threads:[~2017-11-21 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 19:39 [PATCH v2] iomap: report collisions between directio and buffered writes to userspace Darrick J. Wong
2017-11-17 22:56 ` Liu Bo
2017-11-20 16:18 ` Matthew Wilcox
2017-11-20 20:26 ` Dave Chinner
2017-11-20 21:51 ` Matthew Wilcox
2017-11-20 22:27 ` Dave Chinner
2017-11-21 1:37 ` Darrick J. Wong
2017-11-21 4:32 ` Matthew Wilcox
2017-11-21 6:48 ` Dave Chinner
2017-11-21 12:52 ` Matthew Wilcox [this message]
2017-11-21 22:28 ` Dave Chinner
2017-11-22 0:05 ` Darrick J. Wong
2017-11-21 17:23 ` Matthew Wilcox
2017-11-21 18:53 ` Darrick J. Wong
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=20171121125253.GA1484@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=holger@applied-asynchrony.com \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).