From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs: use rhashtable to track buffer cache
Date: Mon, 5 Dec 2016 09:04:11 -0800 [thread overview]
Message-ID: <20161205170411.GA14091@infradead.org> (raw)
In-Reply-To: <20161201103052.28453-3-david@fromorbit.com>
> +static int
> +_xfs_buf_cmp(
> + struct rhashtable_compare_arg *arg,
> + const void *obj)
> +{
> + const struct xfs_buf_map *map = arg->key;
> + const struct xfs_buf *bp = obj;
How about aligning the parameter / variable names here like we
normally do in XFS?
> +static const struct rhashtable_params xfs_buf_hash_params = {
> + .min_size = 32, /* empty/unused AGs have minimal footprint */
> + .nelem_hint = 16,
> + .key_len = sizeof(xfs_daddr_t),
> + .key_offset = offsetof(struct xfs_buf, b_bn),
> + .head_offset = offsetof(struct xfs_buf, b_rhash_head),
> + .automatic_shrinking = true,
> + .obj_cmpfn = _xfs_buf_cmp,
Some tab alignments before the equal signs here?
Also please name the compare function so that it fits the field name,
as that makes grepping so much easier..
.obj_cmpfn = xfs_buf_obj_cmpfn,
Otherwise this looks fine to me and seems to survive testing so far:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2016-12-05 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 10:30 [PATCH 0/3] xfs: miscellaneous improvements for 4.10 Dave Chinner
2016-12-01 10:30 ` [PATCH 1/3] xfs: make xfs btree stats less huge Dave Chinner
2016-12-02 13:20 ` Christoph Hellwig
2016-12-05 1:14 ` Dave Chinner
2016-12-05 12:48 ` Christoph Hellwig
2016-12-01 10:30 ` [PATCH 2/3] xfs: use rhashtable to track buffer cache Dave Chinner
2016-12-05 17:04 ` Christoph Hellwig [this message]
2016-12-07 6:32 ` Dave Chinner
2016-12-01 10:30 ` [PATCH 3/3] xfs: optimise CRC updates Dave Chinner
2016-12-02 13:22 ` Christoph Hellwig
2016-12-04 22:12 ` Dave Chinner
2016-12-05 12:48 ` 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=20161205170411.GA14091@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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;
as well as URLs for NNTP newsgroup(s).