From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: use generic fillattr to reduce redundant code
Date: Tue, 15 Jan 2019 13:13:06 -0800 [thread overview]
Message-ID: <20190115211306.GA12570@infradead.org> (raw)
In-Reply-To: <20190115170849.GC12689@magnolia>
On Tue, Jan 15, 2019 at 09:08:49AM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Refactor xfs_vn_getattr to use generic_fillattr to fill out parts of the
> kstat structure instead of open-coding the same pieces. This eliminates
> redundant code and fixes a bug where we fail to set the AUTOMOUNT
> attribute. Obviously, we retain all the xfs-specific parts.
I find the idea of writing the same values twice for something like
stat that is pretty performane critical rather odd.
I'd much rather just fix the XFS version up to set the automount
attribute, and clear STATX_ATIME for noatime inodes.
next prev parent reply other threads:[~2019-01-15 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 17:08 [PATCH] xfs: use generic fillattr to reduce redundant code Darrick J. Wong
2019-01-15 20:25 ` Dave Chinner
2019-01-15 21:13 ` Christoph Hellwig [this message]
2019-01-15 21:34 ` Christoph Hellwig
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=20190115211306.GA12570@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--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