From: Christoph Hellwig <hch@infradead.org>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [RFC PATCH 1/4] xfs: introduce a new helper xfs_inobt_reada_chunk()
Date: Fri, 15 Nov 2013 09:03:25 -0800 [thread overview]
Message-ID: <20131115170325.GA16942@infradead.org> (raw)
In-Reply-To: <5281F509.7020105@oracle.com>
I like the factoring, but it could go a littler further. Comments
below:
> /*
> + * Loop over all clusters in a chunk for a given incore inode
> + * allocation btree record. Do a readahead if there are any
> + * allocated inodes in that cluster.
> + */
Try to use the full 80 lines available to you for comment.
> + xfs_agblock_t agbno = XFS_AGINO_TO_AGBNO(mp,
> + irec->ir_startino);
> + int nicluster, nbcluster;
> + int chunkidx;
> +
> + nicluster = mp->m_sb.sb_blocksize >= XFS_INODE_CLUSTER_SIZE(mp) ?
> + mp->m_sb.sb_inopblock :
> + (XFS_INODE_CLUSTER_SIZE(mp) >> mp->m_sb.sb_inodelog);
> + nbcluster = nicluster >> mp->m_sb.sb_inopblog;
I'd prefer to factor this out even further. xfs_ialloc_inode_init and
xfs_ifree_cluster already have two pieces of code that calculate these
two (with more readable names) and an additional nuber buffers counter
we won't need here, it might make most sense to factor that into a
single common helper.
> +/*
> + * Lookup clusters in inode chunk for a given incore inobt record,
> + * do readahead if there are any allocated inodes in that cluster.
> + */
> +void xfs_inobt_reada_chunk(struct xfs_mount *mp, xfs_agnumber_t agno,
> + struct xfs_inobt_rec_incore *irec);
No need to duplicate the comment in the header.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-15 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 9:29 [RFC PATCH 1/4] xfs: introduce a new helper xfs_inobt_reada_chunk() Jeff Liu
2013-11-15 17:03 ` Christoph Hellwig [this message]
2013-11-17 12:24 ` Jeff Liu
2013-11-18 11:01 ` Christoph Hellwig
2013-11-18 12:21 ` Jeff Liu
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=20131115170325.GA16942@infradead.org \
--to=hch@infradead.org \
--cc=jeff.liu@oracle.com \
--cc=xfs@oss.sgi.com \
/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